Vulnerability · CVE-2026-118394
Gitea OAuth2 userinfo private group disclosure to public-only tokens
Published Nov 1, 2026 · catalog updated Nov 1, 2026 · Gitea Gitea
Last checked Nov 7, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-118394. EPSS is 0.20%. Act only if a listed version of Gitea Gitea is installed.
Gaps on this record
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-119627 · Unknown
- CVE-2026-119625 · Unknown
- CVE-2026-119533 · Unknown
- CVE-2026-119441 · Unknown
- CVE-2026-118504 · Unknown
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.20%
- Remediation
- Advisory link
- Affected products
- vendor Gitea Gitea
The OAuth2 userinfo endpoint ( ) decided whether to limit the claim to public organizations by re-parsing the header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a public-only OAuth2 token was sent as a query parameter or form field, or a public-only personal access token was used, that scope came back empty and the claim listed the token owner's private organizations, teams and concealed memberships. The disclosure is limited to the owner's organization and team names and memberships; no repository content is exposed. The endpoint now uses the scope of the authenticating token.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Gitea Giteaversion unspecified
How to fix CVE-2026-118394
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
No version range is stored, so an installed version cannot be checked on this page.
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-118394. EPSS is 0.20%. Act only if a listed version of Gitea Gitea is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-200: Exposure of Sensitive Information; CWE-863: Incorrect Authorization. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 1, 2026 · NIST NVD
Detected
The OAuth2 userinfo endpoint ( ) decided whether to limit the claim to public organizations by re-parsing the header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a public-only OAuth2 token was sent as a query parameter or form field, or a public-only personal access token was used, that scope came back empty and the claim listed the to
Nov 1, 2026 · NIST NVD
Updated
The OAuth2 userinfo endpoint ( ) decided whether to limit the claim to public organizations by re-parsing the header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a public-only OAuth2 token was sent as a query parameter or form field, or a public-only personal access token was used, that scope came back empty and the claim listed the to
Sources
- CVE.orgVulnerability recordCVE-2026-118394
The OAuth2 userinfo endpoint ( ) decided whether to limit the claim to public organizations by re-parsing the header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a public-only OAuth2 token was sent as a query paramete
cve.org - FIRST EPSSExploitation probabilityCVE-2026-118394
30-day exploitation probability 0.20%
first.org - NIST NVDVulnerability recordCVE-2026-118394
The OAuth2 userinfo endpoint ( ) decided whether to limit the claim to public organizations by re-parsing the header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a public
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 7, 2026
- CVE.orgNov 2, 2026
- NIST NVDNov 1, 2026