# CVE-2026-82454: Omnivore before android-0.227.0 Authentication Bypass via Apple Sign-in

> Attackers can bypass Apple sign-in authentication in the Omnivore API to impersonate any user by forging JWTs using a known public key.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-8fpq-5wcx-76h3

## What is CVE-2026-82454?

CVE-2026-82454 is a critical authentication bypass vulnerability in omnivore-app omnivore, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-82454?


## How do I fix CVE-2026-82454?

No fix has been published for CVE-2026-82454 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82454 being exploited?

There is no known exploitation of CVE-2026-82454 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82454 and fix it if it is affected.

What it is: CVE-2026-82454 is a critical authentication bypass vulnerability in omnivore-app omnivore, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82454 in the wild and no public exploit code.

Affected product: omnivore-app omnivore. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82454/ (Markdown: https://insights.sbomify.com/CVE-2026-82454/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82454
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82454
- OSV: https://osv.dev/vulnerability/CVE-2026-82454

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82454/
Summaries are generated and may contain mistakes; the official description above is the record.