Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By chainguard

  2. · 29 days later

    Published

  3. · 3 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-105770, by who scored it
Scored byCVSSScoreVector
chainguardCNA (assigner)3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVDNVD · Deferred3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.

Affected products

What to do

Solution: 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.

Workaround: None for self-hosted deployments other than upgrading.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-105770 badge
[![CVE-2026-105770](https://cveledger.app/badge/CVE-2026-105770.svg)](https://cveledger.app/cve/CVE-2026-105770)

Record last updated .