BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-35469High confidence

SpdyStream: DOS on CRI

moby · spdystream

Official source article: GitHub GHSA-PC3F-X583-G7J2 ↗. Check the applicable product and release in the original source.

8.7HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.79% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs moby spdystream and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-github-docker-spdystreamAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcegolang-github-docker-spdystreamAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcegolang-github-docker-spdystreamAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcegolang-github-docker-spdystreamAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-docker-spdystreamUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/moby/spdystreamSEMVER: introduced 0; fixed 0.5.10.5.1OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/moby/spdystream<= 0.5.00.5.1GitHub advisory ↗upstream repository advisory · 8 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-35469 · CSAF 2.0 · revision 36 · interimSUSE Product Security TeamCVE-2026-35469
251 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • containerd as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • containerd-ctr as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • containerd-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • containerd as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • containerd-ctr as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • containerd as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • containerd-ctr as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • containerd as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • containerd-ctr as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • containerized-data-importer as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • containerized-data-importer-manifests as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kubernetes1.23 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes - all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-23298

No EUVD known-exploited evidence

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.7 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

What

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-770
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-23298Official EUVD mapping

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3046IBM Concert: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-1407IBM App Connect Enterprise Certified Container: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise Certified Container ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2026-1950Red Hat OpenShift Container Platform (kubelet, cri-o, kube-apiserver): Schwachstelle ermöglicht Denial of Service

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260422Security Bulletin 22 April 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 April 2026, published on 22 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1125Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2025-21605 Référence CVE CVE-2025-27151 https://www.cve.org/CVERecord?id=CVE-2025-27151 Référence CVE CVE-2025-32023 https://www.cve.org/CVERecord?id=CVE-2025-32023 Référence CVE CVE-2025-48367 https://www.cve.org/CVERecord?id=CVE-2025-48367 Référence CVE CVE-2025-6170 https://www.cve.org/CVERecord?id=CVE-2025-6170 Référence CVE CVE-2026-11856 https://www.cve.org/CVERecord?id=CVE-2026-11856 Référence CVE CVE-2026-13757 https://www.cve.org/CVERecord?id=CVE-2026-13757 Référence CVE CVE-2026-1965 https://www.cve.org/CVERecord?id=CVE-2026-1965 Référence CVE CVE-2026-33818 https://www.cve.org/CVERecord?id=CVE-2026-33818 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3783 https://www.cve.org/CVERecord?id=CVE-2026-3783 Référence CVE CVE-2026-3784 https://www.cve.org/CVERecord?id=CVE-2026-3784 Référence CVE CVE-2026-39822 https://www.cve.org/CVERecord?id=CVE-2026-39822 Référence CVE CVE-2026-41989 https://www.cve.org/CVERecord?id=CVE-2026-41989 Référence CVE CVE-2026-42505 https://www.cve.org/CVERecord?id=CVE-2026-42505 Référence CVE CVE-2026-46600 https://www.cve.org/CVERecord?id=CVE-2026-46600 Référence CVE CVE-2026-4873 https://www.cve.org/CVERecord?id=CVE-2026-4873 Référence CVE CVE-2026-48864 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-34516 Référence CVE CVE-2026-34517 https://www.cve.org/CVERecord?id=CVE-2026-34517 Référence CVE CVE-2026-34518 https://www.cve.org/CVERecord?id=CVE-2026-34518 Référence CVE CVE-2026-34519 https://www.cve.org/CVERecord?id=CVE-2026-34519 Référence CVE CVE-2026-34520 https://www.cve.org/CVERecord?id=CVE-2026-34520 Référence CVE CVE-2026-34525 https://www.cve.org/CVERecord?id=CVE-2026-34525 Référence CVE CVE-2026-34591 https://www.cve.org/CVERecord?id=CVE-2026-34591 Référence CVE CVE-2026-34993 https://www.cve.org/CVERecord?id=CVE-2026-34993 Référence CVE CVE-2026-3520 https://www.cve.org/CVERecord?id=CVE-2026-3520 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3833 https://www.cve.org/CVERecord?id=CVE-2026-3833 Référence CVE CVE-2026-39304 https://www.cve.org/CVERecord?id=CVE-2026-39304 Référence CVE CVE-2026-39824 https://www.cve.org/CVERecord?id=CVE-2026-39824 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40046 https://www.cve.org/CVERecord?id=CVE-2026-40046 Référence CVE CVE-2026-40186 https://www.cve.org/CVERecord?id=CVE-2026-40186 Référence CVE CVE-2026-40347 https://www.cve.org/CVERecord?id=CVE-2026-40347 Référence CVE CVE-2026-40466 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

.cve.org/CVERecord?id=CVE-2026-3537 Référence CVE CVE-2026-3538 https://www.cve.org/CVERecord?id=CVE-2026-3538 Référence CVE CVE-2026-3539 https://www.cve.org/CVERecord?id=CVE-2026-3539 Référence CVE CVE-2026-3540 https://www.cve.org/CVERecord?id=CVE-2026-3540 Référence CVE CVE-2026-3541 https://www.cve.org/CVERecord?id=CVE-2026-3541 Référence CVE CVE-2026-3542 https://www.cve.org/CVERecord?id=CVE-2026-3542 Référence CVE CVE-2026-3543 https://www.cve.org/CVERecord?id=CVE-2026-3543 Référence CVE CVE-2026-3544 https://www.cve.org/CVERecord?id=CVE-2026-3544 Référence CVE CVE-2026-3545 https://www.cve.org/CVERecord?id=CVE-2026-3545 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3731 https://www.cve.org/CVERecord?id=CVE-2026-3731 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-40192 https://www.cve.org/CVERecord?id=CVE-2026-40192 Référence CVE CVE-2026-40200 https://www.cve.org/CVERecord?id=CVE-2026-40200 Référence CVE CVE-2026-4111 https://www.cve.org/CVERecord?id=CVE-2026-4111 Référence CVE CVE-2026-41324 https://www.cve.org/CVERecord?id=CVE-2026-41324 Référence CVE CVE-2026-42308 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2026-34525 Référence CVE CVE-2026-3479 https://www.cve.org/CVERecord?id=CVE-2026-3479 Référence CVE CVE-2026-3497 https://www.cve.org/CVERecord?id=CVE-2026-3497 Référence CVE CVE-2026-34986 https://www.cve.org/CVERecord?id=CVE-2026-34986 Référence CVE CVE-2026-35236 https://www.cve.org/CVERecord?id=CVE-2026-35236 Référence CVE CVE-2026-35237 https://www.cve.org/CVERecord?id=CVE-2026-35237 Référence CVE CVE-2026-35238 https://www.cve.org/CVERecord?id=CVE-2026-35238 Référence CVE CVE-2026-35239 https://www.cve.org/CVERecord?id=CVE-2026-35239 Référence CVE CVE-2026-35240 https://www.cve.org/CVERecord?id=CVE-2026-35240 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3644 https://www.cve.org/CVERecord?id=CVE-2026-3644 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40192 https://www.cve.org/CVERecord?id=CVE-2026-40192 Référence CVE CVE-2026-41066 https://www.cve.org/CVERecord?id=CVE-2026-41066 Référence CVE CVE-2026-4111 https://www.cve.org/CVERecord?id=CVE-2026-4111 Référence CVE CVE-2026-4224 https://www.cve.org/CVERecord?id=CVE-2026-4224 Référence CVE CVE-2026-4424 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0456Multiples vulnérabilités dans les produits Microsoft

De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 16 Apr 2026 · Last source change 11 Sept 2026, 12:09 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-23298
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:66521.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:66521
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:66521.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:66521
    github.com ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:63046.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:63046
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2
    CNA ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:63046.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:63046
    github.com ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:60023.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:60023
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2
    CNA ↗
  6. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:60023.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:60023
    github.com ↗
  7. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:61314.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:61314
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2
    CNA ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:61314.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:61314
    github.com ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 0.5.1 · Fixed: 0.5.1.
    After
    spdystream: < 0.5.1 · Fixed: RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9
    CNA ↗
  10. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:59557.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:59557
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2
    CNA ↗
  11. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:59557.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:59557
    github.com ↗
  12. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:56431.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:56431
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2
    CNA ↗
  13. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:56431.
    Before
    remediation: github.com/GHSA-pc3f-x583-g7j2
    After
    remediation: github.com/GHSA-pc3f-x583-g7j2 · vendor advisory: access.redhat.com/RHSA-2026:56431
    github.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-23298↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference · GitHub GHSA-PC3F-X583-G7J2↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-35469 · cve.blacktree.nl