# CVE-2026-110210: Phase Console through 2.77.3 Missing Authorization via secretHistory GraphQL Query

> Attackers with an environment key can read secret history via GraphQL, bypassing authorization checks to access encrypted secrets.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-mw5f-8wgh-2m29

## What is CVE-2026-110210?

CVE-2026-110210 is a medium-severity missing authorization vulnerability in Phase Console, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Phase Console through 2.77.3 contains a missing authorization vulnerability that allows organisation members without Secrets read permission to read secret history via the secretHistory GraphQL query. Attackers holding an environment key can supply a known secret identifier to retrieve encrypted secret events and decrypt values using their wrapped environment key.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110210 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110210 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110210 is a medium-severity missing authorization vulnerability in Phase Console, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110210 exists.

Affected product: Phase Console. 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-110210/ (Markdown: https://insights.sbomify.com/CVE-2026-110210/index.md)
```

## Sources

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

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