CVE-2026-82454

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.1Exploit: None knownExposed: 0

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

The Omnivore API (packages/api) before the fix in commit abf53d6 contains an authentication bypass in Apple sign-in token verification. The decodeAppleToken function extracted the 'alg' field from the attacker-supplied JWT header and passed it as the sole allowed algorithm to jwt.verify(). Using jsonwebtoken v8 (which does not validate key/algorithm compatibility), an attacker can set alg=HS256 and sign a forged token using Apple's publicly available RSA public key as the HMAC secret, bypassing signature verification and impersonating any Apple-linked account.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
45(Track)
EG Risk 45/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 29, 2026

Last Modified

August 29, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
Patch available. Sources: github_pr, github_commit.
generic

Omnivore before android-0.227.0 Authentication Bypass via Apple Sign-in | Advisories | VulnCheck

https://www.vulncheck.com/advisories/omnivore-before-android-0.227.0-authentication-bypass-via-apple-sign-in
github_pr Patch Available

fix: hardcode RS256 in Apple JWT verification to prevent algorithm co…

Patch available: omnivore-app/omnivore android-0.227.0 (PR #4652 merged 2026-08-25)

https://github.com/omnivore-app/omnivore/pull/4652
github_commit Patch Available

commit abf53d650875 (omnivore-app/omnivore)

Patch available: omnivore-app/omnivore android-0.227.0 (contains commit abf53d650875)

https://github.com/omnivore-app/omnivore/commit/abf53d6508755d3d22a994e28e370a9193ea977a
generic

GitHub - omnivore-app/omnivore: Omnivore is a complete, open source read-it-later solution for people who like reading. · GitHub

https://github.com/omnivore-app/omnivore

Vendor Advisories for CVE-2026-82454(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 8× in last 7d / 8× 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-30 05:59 UTCGHSA enrichment
  2. 2026-08-30 02:04 UTCGHSA enrichment
  3. 2026-08-29 22:11 UTCGHSA enrichment
  4. 2026-08-29 18:16 UTCEG score recompute
  5. 2026-08-29 18:16 UTCGHSA enrichment
  6. 2026-08-29 14:23 UTCEG score recompute
  7. 2026-08-29 13:53 UTCEG score recompute
  8. 2026-08-29 13:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-82454?
CVE-2026-82454 is a critical vulnerability published on August 29, 2026. The Omnivore API (packages/api) before the fix in commit abf53d6 contains an authentication bypass in Apple sign-in token verification. The decodeAppleToken function extracted the 'alg' field from the attacker-supplied JWT header and passed it as the sole allowed algorithm to jwt.verify(). Using…
When was CVE-2026-82454 disclosed?
CVE-2026-82454 was first published in the National Vulnerability Database on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-82454?
CVE-2026-82454 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-82454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82454, 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-82454

Explore →

Is Your Infrastructure Affected by CVE-2026-82454?

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

Start Free Scan →Browse All CVEs