CVE-2022-39280: dparse is a parser for Python dependency files

Q: How do I fix CVE-2022-39280?

dependency parser: upgrade to 0.5.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-39280 being exploited?

CVE-2022-39280 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-39280 affect?

CVE-2022-39280 affects dependency parser. Severity is medium (CVSS 5.9). dparse is a parser for Python dependency files. dparse in versions before 0.5.2 contain a regular expression that is vulnerable to a Regular Expression Denial of Service. All the users parsing index server URLs with dparse are impacted by t

Q: How urgent is CVE-2022-39280?

Priority 43/100. Remotely exploitable, no login, no user action

This month

MEDIUM 5.9REMOTEUPGRADE

CVE-2022-39280 is a medium-severity flaw (CVSS 5.9) affecting dependency parser. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

dparse is a parser for Python dependency files. dparse in versions before 0.5.2 contain a regular expression that is vulnerable to a Regular Expression Denial of Service. All the users parsing index server URLs with dparse are impacted by this vulnerability. A patch has been applied in version `0.5.2`, all the users are advised to upgrade to `0.5.2` as soon as possible. Users unable to upgrade should avoid passing index server URLs in the source

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Weakness	CWE-400, CWE-1333
Published	2022-10-06
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: pyup

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-06 18:16 UTCPublished CVE record published
2026-06-17 04:58 UTCUpdated Record last modified

pyup dependency parser UPGRADE

Affected: < 0.5.1

Fixed in: 0.5.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dependency-parser || rpm -q dependency-parser || dependency-parser --version

2. UPGRADE to 0.5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dependency-parser

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dependency-parser

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-39280?

dependency parser: upgrade to 0.5.1. Exact commands for each OS are on this page.

Is CVE-2022-39280 being exploited?

CVE-2022-39280 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-39280 affect?

CVE-2022-39280 affects dependency parser. Severity is medium (CVSS 5.9). dparse is a parser for Python dependency files. dparse in versions before 0.5.2 contain a regular expression that is vulnerable to a Regular Expression Denial of Service. All the users parsing index server URLs with dparse are impacted by t

How urgent is CVE-2022-39280?

Priority 43/100. Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

References

← Back to latest CVEs