<?xml version="1.0" encoding="UTF-8"?>
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
  <DocumentTitle xml:lang="en">Security update for sbctl</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>openSUSE-SU-2026:20105-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2026-01-23T10:02:42Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2026-01-23T10:02:42Z</InitialReleaseDate>
    <CurrentReleaseDate>2026-01-23T10:02:42Z</CurrentReleaseDate>
    <Generator>
      <Engine>cve-database/bin/generate-cvrf.pl</Engine>
      <Date>2017-02-24T01:00:00Z</Date>
    </Generator>
  </DocumentTracking>
  <DocumentNotes>
    <Note Title="Topic" Type="Summary" Ordinal="1" xml:lang="en">Security update for sbctl</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">This update for sbctl fixes the following issues:

Changes in sbctl:

- Upgrade the embedded golang.org/x/net to 0.46.0
  * Fixes: bsc#1251399, CVE-2025-47911: various algorithms with
    quadratic complexity when parsing HTML documents
  * Fixes: bsc#1251609, CVE-2025-58190: excessive memory consumption
    by 'html.ParseFragment' when processing specially crafted input

- Update to version 0.18:
  * logging: fixup new go vet warning
  * workflows: add cc for cross compile
  * workflow: add sudo to apt
  * workflow: add pcsclite to ci
  * workflow: try enable cgo
  * go.mod: update golang.org/x/ dependencies
  * fix: avoid adding bogus Country attribute to subject DNs
  * sbctl: only store file if we did actually sign the file
  * installkernel: add post install hook for Debian's traditional installkernel
  * CI: missing libpcsclite pkg
  * workflows: add missing depends and new pattern keyword
  * Add yubikey example for create keys to the README
  * Initial yubikey backend keytype support
  * verify: ensure we pass args in correct order

- bsc#1248949 (CVE-2025-58058):
  Bump xz to 0.5.14

- Update to version 0.17:
  * Ensure we don't wrongly compare input/output files when signing
  * Added --json supprt to sbctl verify
  * Ensure sbctl setup with no arguments returns a helpful output
  * Import latest Microsoft keys for KEK and db databases
  * Ensure we print the path of the file when encountering an invalid PE file
  * Misc fixups in tests
  * Misc typo fixes in prints

- Update to version 0.16:
  * Ensure sbctl reads --config even if /etc/sbctl/sbctl.conf is
    present
  * Fixed a bug where sbctl would abort if the TPM eventlog
    contains the same byte multiple times
  * Fixed a landlock bug where enroll-keys --export did not work
  * Fixed a bug where an ESP mounted to multiple paths would not be
    detected
  * Exporting keys without efivars present work again
  * sbctl sign will now use the saved output path if the signed
    file is enrolled
  * enroll-keys --append will now work without --force.
- Updates from version 0.15.4:
  * Fixed an issue where sign-all did not report a non-zero exit
    code when something failed
  * Fixed and issue where we couldn't write to a file with landlock
  * Fixed an issue where --json would print the human readable
    output and the json
  * Fixes landlock for UKI/bundles by disabling the sandbox feature
  * Some doc fixups that mentioned /usr/share/
</Note>
    <Note Title="Terms of Use" Type="Legal Disclaimer" Ordinal="3" xml:lang="en">The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).</Note>
    <Note Title="Patchnames" Type="Details" Ordinal="4" xml:lang="en">openSUSE-Leap-16.0-packagehub-93</Note>
  </DocumentNotes>
  <DocumentDistribution xml:lang="en">Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0)</DocumentDistribution>
  <DocumentReferences>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1248949</URL>
      <Description>SUSE Bug 1248949</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1251399</URL>
      <Description>SUSE Bug 1251399</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1251609</URL>
      <Description>SUSE Bug 1251609</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-47911/</URL>
      <Description>SUSE CVE CVE-2025-47911 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-58058/</URL>
      <Description>SUSE CVE CVE-2025-58058 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-58190/</URL>
      <Description>SUSE CVE CVE-2025-58190 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="openSUSE Leap 16.0">
      <Branch Type="Product Name" Name="openSUSE Leap 16.0">
        <FullProductName ProductID="openSUSE Leap 16.0">openSUSE Leap 16.0</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="sbctl-0.18-bp160.1.1">
      <FullProductName ProductID="sbctl-0.18-bp160.1.1">sbctl-0.18-bp160.1.1</FullProductName>
    </Branch>
    <Relationship ProductReference="sbctl-0.18-bp160.1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Leap 16.0">
      <FullProductName ProductID="openSUSE Leap 16.0:sbctl-0.18-bp160.1.1">sbctl-0.18-bp160.1.1 as a component of openSUSE Leap 16.0</FullProductName>
    </Relationship>
  </ProductTree>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="1">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">unknown</Note>
    </Notes>
    <CVE>CVE-2025-47911</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Leap 16.0:sbctl-0.18-bp160.1.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-47911.html</URL>
        <Description>CVE-2025-47911</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1251308</URL>
        <Description>SUSE Bug 1251308</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="2">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.</Note>
    </Notes>
    <CVE>CVE-2025-58058</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Leap 16.0:sbctl-0.18-bp160.1.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-58058.html</URL>
        <Description>CVE-2025-58058</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1248889</URL>
        <Description>SUSE Bug 1248889</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="3">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">unknown</Note>
    </Notes>
    <CVE>CVE-2025-58190</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Leap 16.0:sbctl-0.18-bp160.1.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-58190.html</URL>
        <Description>CVE-2025-58190</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1251309</URL>
        <Description>SUSE Bug 1251309</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
