# CVE-2026-71214: NASA-AMMOS plandev - Client-Supplied session_variables Bypass Hasura-Origin Authorization in sequencing-server

> Attackers can bypass Hasura-origin authorization by supplying session variables in the request body, gaining unauthorized access to the sequencing server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-x4pc-pqfq-54j2

## What is CVE-2026-71214?

CVE-2026-71214 is a critical authentication bypass vulnerability in NASA-AMMOS plandev (sequencing-server), published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Aerie/PlanDev sequencing-server's authorization middleware (sequencing-server/src/app.ts) derives the caller's Hasura session role via getHasuraSession, which prefers a session_variables object taken directly from the client-supplied JSON request body over the Authorization header's JWT claims, with no verification that the request actually originated from Hasura.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-71214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71214 is a critical authentication bypass vulnerability in NASA-AMMOS plandev (sequencing-server), published on 5 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-71214 in the wild and no public exploit code.

Affected product: NASA-AMMOS plandev (sequencing-server). 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-71214/ (Markdown: https://insights.sbomify.com/CVE-2026-71214/index.md)
```

## Sources

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

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