CVE-2026-62995

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.3Exploit: None knownExposed: 0

A fix is available — apply it.

joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. in versions 1.7.1 and prior, joserfc accepts JWTs with trailing padding (==) which are not conforming to the JOSE specifications. This leads to malleability of the JWTs when consumed by joserfc. Depending on this application this might or not be an issue. This could lead to bypass of token revocation or anti-replay protection when implemented as a deny list of tokens or a deny list of token hashes. Note that ECDSA JWS are always malleable because of the malleability of ECDSA signatures (first test case in the code bellow). This makes a scheme which assumes that JWTs are not malleable brittle. However for other signatures (or MAC) schemes it might make sense to assume non malleability of the token. This issue has been fixed in version 1.7.2.

CVSS v3
2.3
EG Score
2.3(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity23% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

References (1)

Vendor Advisories for CVE-2026-62995(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjaeger-main-2.20.0-0.8.hum12026-07-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
joserfc1.1.0-1 ... 1.7.4-1 (22 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
joserfc1.1.0-1 ... 1.7.1-1 (19 versions)1.7.2-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 18:01 UTCEG score recompute
  3. 2026-08-14 18:01 UTCVendor advisory
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-11 18:28 UTCEG score recompute
  7. 2026-08-11 18:28 UTCVendor advisory
  8. 2026-08-09 13:47 UTCEPSS rescore
  9. 2026-08-08 18:54 UTCEG score recompute
  10. 2026-08-08 18:54 UTCVendor advisory
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-06 13:47 UTCEPSS rescore
  13. 2026-08-05 19:20 UTCEG score recompute
  14. 2026-08-05 19:20 UTCVendor advisory
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 10:39 UTCEPSS rescore
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-02 19:47 UTCEG score recompute
  21. 2026-08-02 19:47 UTCVendor advisory
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 20:13 UTCEG score recompute
  24. 2026-07-30 20:13 UTCVendor advisory
  25. 2026-07-30 16:28 UTCEPSS rescore
Show 7 more
  1. 2026-07-30 15:38 UTCEG score recompute
  2. 2026-07-30 15:38 UTCVendor advisory
  3. 2026-07-30 15:00 UTCEG score recompute
  4. 2026-07-30 15:00 UTCVendor advisory
  5. 2026-07-29 19:32 UTCEG score recompute
  6. 2026-07-29 18:34 UTCEG score recompute
  7. 2026-07-29 18:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62995?
CVE-2026-62995 is a low vulnerability published on July 29, 2026. joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. in versions 1.7.1 and prior, joserfc accepts JWTs with trailing padding (==) which are not conforming to the JOSE specifications. This leads to malleability of the JWTs when…
When was CVE-2026-62995 disclosed?
CVE-2026-62995 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62995 actively exploited?
CVE-2026-62995 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-62995?
CVE-2026-62995 has a CVSS v3 base score of 2.3 (NVD).
How do I remediate CVE-2026-62995?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62995, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62995

Explore →

Is Your Infrastructure Affected by CVE-2026-62995?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs