LiveActive security incident?Get immediate response
CVE Record

CVE-2016-6580: A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could...

A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could be targeted by a malicious peer by having that peer assign priority information for every possible HTTP/2 stream ID. The priority tree would happily continue to store the priority information for each stream, and would therefore allocate unbounded amounts of memory. Attempting to actually use a tree like this would also cause extremely high CPU usage to maintain the tree.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a denial-of-service flaw in Python's priority library, used by some HTTP/2 implementations. A malicious peer could make the service store priority data for every possible stream ID, consuming unbounded memory and high CPU. Sources do not provide CVSS, known exploitation, or named affected products beyond uses of priority before 1.2.0. Exposure is most likely in Python applications, services, or dependencies that implement HTTP/2 using priority versions earlier than 1.2.0. The bundle does not identify specific downstream products or deployments. Treat as a targeted availability risk, not confirmed active exploitation. It deserves remediation where HTTP/2 services are reachable by untrusted peers, especially for customer-facing or operationally critical systems. Mitigation focus: Upgrade Python priority to version 1.2.0 or later where directly used.; Check downstream HTTP/2 frameworks for bundled or pinned vulnerable priority versions.; Review vendor advisories for products that embed Python priority indirectly..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-6580 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.