CVE-2016-6580

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

1.8% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-01-10 15:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:51 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.8% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-01-10 15:59 UTC

Last modified

2026-06-17 00:51 UTC

Exploit probability

1.8% · EPSS, next 30 days

Weakness

CWE-399

Record status

Modified

Affected

• Python Priority Library 1.0.0
• Python Priority Library 1.1.0
• Python Priority Library 1.1.1

Attack profile CVSS 3.0 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-6580.md and follow it. Check whether this project is affected by CVE-2016-6580. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge