Skip to main content

Dvc: PyJWT Issuer field partial matches allowed (CVE-2024-53861)

0
Low
Published: 08/13/2026 (08/13/2026, 16:44:03 UTC)
Source: GCVE Database
Product: dvc

Description

A vulnerability in PyJWT's issuer (iss) claim validation allows partial string matches instead of exact matches. This occurs because the code mistakenly treats the issuer string as a sequence, causing substring checks rather than equality checks. The issue affects DVC versions from 3.56.0_2 up to but not including 3.58.0. Although the signature validation remains intact, this flaw could allow tokens with incorrect issuer claims to be accepted. The vulnerability has a low severity score and a patch is available.

CVSS v3.1

Score 2.2low

Attack Vector
Network
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

Affected software

Homebrewmore threats →ghsa
dvc
pkg:brew/dvc
Affected versions
>=3.56.0_2 <3.58.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/18/2026, 01:42:56 UTC

Technical Analysis

CVE-2024-53861 is a vulnerability in PyJWT's issuer claim validation introduced in version 2.10.0. The code changed the issuer check from verifying if the issuer is a list to checking if it is a Sequence. Since strings are sequences, this caused the 'in' operator to perform substring matching rather than exact equality. As a result, an issuer value like "acb" would be accepted for a token with issuer "_abc_". This flaw affects DVC versions >=3.56.0_2 and <3.58.0, which use this PyJWT version. The signature verification remains required, limiting the impact.

Potential Impact

The vulnerability allows tokens with issuer claims that partially match the expected issuer string to be accepted, potentially bypassing strict issuer validation. However, since the token signature must still be valid, the overall impact is limited. The CVSS score is 2.2 (low), indicating minimal impact on confidentiality, integrity, and availability.

Mitigation Recommendations

A patch is available to correct the issuer claim validation logic to require exact matches rather than substring matches. Users of affected DVC versions (>=3.56.0_2 <3.58.0) should upgrade to a fixed version once released. Until then, be aware of the issuer validation weakness but note that signature verification remains enforced.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BREW-dvc-CVE-2024-53861
Osv Schema Version
1.7.3
Ecosystems
["Homebrew"]
Cvss Version
3.1

Threat ID: 6aac8e3355bf5e2cf5491209

Added to database: 09/18/2026, 01:04:51 UTC

Last enriched: 09/18/2026, 01:42:56 UTC

Last updated: 09/18/2026, 01:42:56 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses