<?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 rekor</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE-SU-2026:0383-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2026-02-04T12:46:28Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2026-02-04T12:46:28Z</InitialReleaseDate>
    <CurrentReleaseDate>2026-02-04T12:46:28Z</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 rekor</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">This update for rekor fixes the following issues:

Security fixes:

- CVE-2025-58058: Fixed github.com/ulikunitz/xz leaks memory (bsc#1248910)
- CVE-2025-29923: Fixed potential out of order responses when `CLIENT SETINFO` 
  times out during connection establishment (bsc#1241153)

Other fixes:

- Update to version 1.4.3
- Update to version 1.4.2
- Update to version 1.4.1 (jsc#SLE-23476)
</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">SUSE-2026-383,SUSE-SLE-Module-Basesystem-15-SP7-2026-383,openSUSE-SLE-15.6-2026-383</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/update/announcement/2026/suse-su-20260383-1/</URL>
      <Description>Link for SUSE-SU-2026:0383-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2026-February/024058.html</URL>
      <Description>E-Mail link for SUSE-SU-2026:0383-1</Description>
    </Reference>
    <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/1241153</URL>
      <Description>SUSE Bug 1241153</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1248910</URL>
      <Description>SUSE Bug 1248910</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2025-29923/</URL>
      <Description>SUSE CVE CVE-2025-29923 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>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Module for Basesystem 15 SP7">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Module for Basesystem 15 SP7">
        <FullProductName ProductID="SUSE Linux Enterprise Module for Basesystem 15 SP7" CPE="cpe:/o:suse:sle-module-basesystem:15:sp7">SUSE Linux Enterprise Module for Basesystem 15 SP7</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Family" Name="openSUSE Leap 15.6">
      <Branch Type="Product Name" Name="openSUSE Leap 15.6">
        <FullProductName ProductID="openSUSE Leap 15.6" CPE="cpe:/o:opensuse:leap:15.6">openSUSE Leap 15.6</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="rekor-1.4.3-150400.4.28.1">
      <FullProductName ProductID="rekor-1.4.3-150400.4.28.1">rekor-1.4.3-150400.4.28.1</FullProductName>
    </Branch>
    <Relationship ProductReference="rekor-1.4.3-150400.4.28.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Module for Basesystem 15 SP7">
      <FullProductName ProductID="SUSE Linux Enterprise Module for Basesystem 15 SP7:rekor-1.4.3-150400.4.28.1">rekor-1.4.3-150400.4.28.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP7</FullProductName>
    </Relationship>
    <Relationship ProductReference="rekor-1.4.3-150400.4.28.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Leap 15.6">
      <FullProductName ProductID="openSUSE Leap 15.6:rekor-1.4.3-150400.4.28.1">rekor-1.4.3-150400.4.28.1 as a component of openSUSE Leap 15.6</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">go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.3, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.3. You can prevent the vulnerability by setting the flag DisableIndentity to true when constructing the client instance.</Note>
    </Notes>
    <CVE>CVE-2025-29923</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Module for Basesystem 15 SP7:rekor-1.4.3-150400.4.28.1</ProductID>
        <ProductID>openSUSE Leap 15.6:rekor-1.4.3-150400.4.28.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>https://www.suse.com/support/update/announcement/2026/suse-su-20260383-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2025-29923.html</URL>
        <Description>CVE-2025-29923</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1241152</URL>
        <Description>SUSE Bug 1241152</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>SUSE Linux Enterprise Module for Basesystem 15 SP7:rekor-1.4.3-150400.4.28.1</ProductID>
        <ProductID>openSUSE Leap 15.6:rekor-1.4.3-150400.4.28.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>https://www.suse.com/support/update/announcement/2026/suse-su-20260383-1/</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>
</cvrfdoc>
