# CVE-2026-105770: Octo STS discloses trust policy contents to unauthorized callers via Exchange error messages

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

Octo STS (github.com/octo-sts/app) before 0.11.2 returns trust policy configuration to callers whose OIDC token does not satisfy that policy. TrustPolicy.CheckToken included the policy's issuer, subject and audience values or patterns and claim_pattern names and regular expressions in its PermissionDenied errors, which Exchange returned verbatim. Exchange also selected the GitHub App installation before checking the token, so errors from resolving the policy's app or app_pattern pin were returned to callers the policy does not trust. An attacker who holds any validly signed OIDC token, such as a GitHub Actions token from a repository they own, and who knows or guesses a target owner/repo and identity name can read that policy's matching rules, even when the policy is stored in a private repository. These rules often name internal repositories, branches, environments or cloud account identifiers. The issue does not allow minting tokens or bypassing a trust policy. This issue is fixed in 0.11.2.

## Remediation

- fix: Upgrade to Octo STS 0.11.2 or later. The token is now checked against the trust policy immediately after the policy is loaded and before installation selection or app pin resolution. On a mismatch the detailed reason is logged and recorded on the operator audit event, and the caller receives only a generic "PermissionDenied: token does not match trust policy". Policies that exist but cannot be read, parsed or compiled now return the same NotFound response as a missing policy. Users of the hosted service are protected once the fix is deployed. (source: CNA: chainguard)
- workaround: None for self-hosted deployments other than upgrading. (source: CNA: chainguard)
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: chainguard) — https://github.com/octo-sts/app/commit/88c6432adc4f497ec69b574e1ce162a564a9e71a

## Affected products and versions

- octo-sts / app (github.com/octo-sts/app): ≥ 0; < 0.11.2 (affected, semver). Source: CNA: chainguard

## Severity and prioritization

- CVSS 3.1: 5.3 (medium); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N; source: CNA: chainguard

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-209

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/octo-sts/app/security/advisories/GHSA-h5p6-j8m9-xx4p (CNA: chainguard; vendor-advisory)

- https://github.com/octo-sts/app/commit/88c6432adc4f497ec69b574e1ce162a564a9e71a (CNA: chainguard; patch)

- https://github.com/octo-sts/app/releases/tag/v0.11.2 (CNA: chainguard; release-notes)

## Provenance

- CNA: chainguard: https://www.cve.org/CVERecord?id=CVE-2026-105770; retrieved 2026-11-03; source updated 2026-11-03

Revision: 9de8972632c110bb745298f57fe8171627f96222161474823538d3a30d98aec2

Canonical: https://y2.dev/cve/CVE-2026-105770

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.