CVE-2026-13089

NONECVSS 0.0Trending — 5 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify.

When the caller does not pin an algorithm, OIDC::Lite::Model::IDToken::verify sets $self->alg($self->header->{alg}) from the token's own header and then calls decode_jwt(token, key, 1, [$self->alg]), handing JSON::WebToken an accepted-algorithm allowlist taken from the untrusted token. A token with alg=none yields ['none'], so decode_jwt returns the claims with no signature check, and a token with alg=HS256 is verified with the RP's RSA public key as the HMAC secret (RS to HS confusion).

The ID Token is the OpenID Connect authentication assertion delivered to the Relying Party. Any caller that verifies an ID Token through the unpinned load(token)->verify path, or load(token, key) with only the key pinned, accepts a forged token carrying attacker-chosen claims such as sub and is authenticated as any user. Passing an explicit algorithm so $self->alg is already set bypasses the header-derived allowlist and is not affected.

Note that the latest version uploaded to CPAN is 0.10. Later versions are available in the git repository.

CVSS v3
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

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. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
6.6%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 23, 2026

References (4)

Vendor Advisories for CVE-2026-13089(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 41× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 23:24 UTCNVD update
  4. 2026-07-22 23:23 UTCEG score recompute
  5. 2026-07-22 23:23 UTCGHSA enrichment
  6. 2026-07-22 23:20 UTCGHSA enrichment
  7. 2026-07-22 23:19 UTCGHSA enrichment
  8. 2026-07-22 23:17 UTCGHSA enrichment
  9. 2026-07-22 23:16 UTCGHSA enrichment
  10. 2026-07-22 23:15 UTCGHSA enrichment
  11. 2026-07-22 23:14 UTCGHSA enrichment
  12. 2026-07-22 23:12 UTCGHSA enrichment
  13. 2026-07-22 23:10 UTCGHSA enrichment
  14. 2026-07-22 23:09 UTCGHSA enrichment
  15. 2026-07-22 23:08 UTCGHSA enrichment
  16. 2026-07-22 23:08 UTCGHSA enrichment
  17. 2026-07-22 23:07 UTCGHSA enrichment
  18. 2026-07-22 23:05 UTCGHSA enrichment
  19. 2026-07-22 23:04 UTCGHSA enrichment
  20. 2026-07-22 23:03 UTCGHSA enrichment
  21. 2026-07-22 23:01 UTCGHSA enrichment
  22. 2026-07-22 23:00 UTCGHSA enrichment
  23. 2026-07-22 22:59 UTCGHSA enrichment
  24. 2026-07-22 22:58 UTCGHSA enrichment
  25. 2026-07-22 22:57 UTCGHSA enrichment
Show 16 more
  1. 2026-07-22 22:56 UTCGHSA enrichment
  2. 2026-07-22 22:55 UTCGHSA enrichment
  3. 2026-07-22 22:54 UTCGHSA enrichment
  4. 2026-07-22 22:53 UTCGHSA enrichment
  5. 2026-07-22 22:52 UTCGHSA enrichment
  6. 2026-07-22 22:51 UTCGHSA enrichment
  7. 2026-07-22 22:50 UTCGHSA enrichment
  8. 2026-07-22 22:47 UTCGHSA enrichment
  9. 2026-07-22 22:45 UTCGHSA enrichment
  10. 2026-07-22 22:41 UTCGHSA enrichment
  11. 2026-07-22 22:39 UTCMITRE cvelistV5
  12. 2026-07-22 21:58 UTCEG score recompute
  13. 2026-07-22 21:58 UTCGHSA enrichment
  14. 2026-07-22 21:23 UTCNVD update
  15. 2026-07-22 20:58 UTCEG score recompute
  16. 2026-07-22 20:56 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-13089?
CVE-2026-13089 is a none vulnerability published on July 22, 2026. OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify. When the caller does not pin an algorithm, OIDC::Lite::Model::IDToken::verify sets $self->alg($self->header->{alg}) from the token's own header and then…
When was CVE-2026-13089 disclosed?
CVE-2026-13089 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13089 actively exploited?
CVE-2026-13089 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-13089?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13089, 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

Explore the affected products and dependency analysis for CVE-2026-13089

Explore →

Is Your Infrastructure Affected by CVE-2026-13089?

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