VulnerabilityPublished 3 Nov 2026

CVE-2026-105770: octo-sts app · Generation of Error Message Containing Sensitive Information

Affects octo-sts appSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.11.2 when convenient.

Data as of 3 Nov 2026, 01:13 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (chainguard)	CVSS 3.1	5.3

Patch: Available – fixed in 0.11.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade app and github.com/octo-sts/app to 0.11.2.

Affected software

Product	Affected	Fixed in
appgithub.com/octo-sts/app	Affected <0.11.2	Fixed in 0.11.2
Gogithub.com/octo-sts/app`pkg:golang/github.com/octo-sts/app`Other threats	Affected <0.11.2	Fixed in 0.11.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Octo STS to version 0.11.2 or later, where this information disclosure vulnerability is fixed. No other mitigation is required as the issue is resolved in the fixed version.

Description

Octo STS versions before 0.11.2 contain a vulnerability where error messages expose sensitive trust policy configuration details. Specifically, when an OIDC token does not satisfy a trust policy, the error messages returned include issuer, subject, audience values, claim pattern names, and regular expressions. This information disclosure can reveal internal repository names, branches, environments, or cloud account identifiers. The vulnerability does not allow token minting or bypassing the trust policy. The issue is fixed in version 0.11.2.

Impact

An attacker with any valid OIDC token and knowledge or guess of a target repository and identity can obtain sensitive trust policy configuration details via error messages. This information disclosure can reveal internal repository names, branches, environments, or cloud account identifiers. However, the vulnerability does not allow the attacker to mint tokens or bypass trust policies.

Summary

Octo STS (app) prior to version 0.11.2 has a CWE-209 vulnerability where error messages generated by TrustPolicy.CheckToken include sensitive trust policy configuration details such as issuer, subject, audience, and claim patterns. These error messages are returned verbatim by the Exchange component, potentially exposing internal policy matching rules to an attacker holding any validly signed OIDC token (e.g., a GitHub Actions token) who can guess a target owner/repo and identity name. This exposure can leak sensitive internal information stored in private repositories. The vulnerability does not enable token minting or trust policy bypass. The vulnerability is resolved in version 0.11.2.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 01:00 UTC

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats