Octo STS discloses trust policy contents to unauthorized callers via Exchange error messages
Summary
| CVE | CVE-2026-105770 |
|---|---|
| State | PUBLISHED |
| Assigner | chainguard |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-03 01:16:44 UTC |
| Updated | 2026-11-03 16:30:49 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 5.3 MEDIUM from 82cea9a6-e9e3-46fe-bdb0-3673de380178
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Problem Types: CWE-209 | CWE-209 CWE-209: Generation of Error Message Containing Sensitive Information
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 82cea9a6-e9e3-46fe-bdb0-3673de380178 | Secondary | 5.3 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| 3.1 | CNA | CVSS | 5.3 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
CVSS v3.1 Breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/octo-sts/app/commit/88c6432adc4f497ec69b574e1ce162a564a9e71a | 82cea9a6-e9e3-46fe-bdb0-3673de380178 | github.com | |
| github.com/octo-sts/app/releases/tag/v0.11.2 | 82cea9a6-e9e3-46fe-bdb0-3673de380178 | github.com | |
| github.com/octo-sts/app/security/advisories/GHSA-h5p6-j8m9-xx4p | 82cea9a6-e9e3-46fe-bdb0-3673de380178 | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Utkarsh Baghel (hackerrexx) (en)
Additional Advisory Data
Solutions
CNA: 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.
Workarounds
CNA: None for self-hosted deployments other than upgrading.