© 2026 vulntracker.io

CVE-2016-6580

N/A

Published: January 10, 2017 at 03:00 PM UTC

Updated: June 17, 2026 at 12:51 AM UTC

1 product affected across 1 vendorPython Priority Library

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Python Priority Library · Python

95%

1.0.0 1.1.0 1.1.1

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html

References (2)

VDB Entryx_refsource_BIDThird Party Advisory

Source: [email protected]

http://www.securityfocus.com/bid/92311

x_refsource_CONFIRMMitigationVendor Advisory

Source: [email protected]

https://python-hyper.org/priority/en/latest/security/CVE-2016-6580.html

CVSS

5MEDIUM[email protected]

Confidentiality: NONE
Integrity: NONE
Availability: PARTIAL

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-399

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card