octo-sts Octo STS up to 0.11.1 TrustPolicy TrustPolicy.CheckToken information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, has been found in octo-sts Octo STS up to 0.11.1. The impacted element is the function TrustPolicy.CheckToken of the component TrustPolicy. The manipulation leads to information disclosure. This vulnerability is documented as CVE-2026-105770. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in octo-sts Octo STS up to 0.11.1 and classified as problematic. This issue affects the function TrustPolicy.CheckToken of the component TrustPolicy. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-105770 since 10/05/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 0.11.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-115653). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• octo-sts

Name

• Octo STS

Version

• 0.11.0
• 0.11.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion