Skip to content
Fencer Intel
low 3.1

CVE-2026-23603 json

Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim

published 3mo ago modified 2mo ago also GHSA-x77v-q46j-393g , GO-2026-6083 , EUVD-2026-58134

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim

Patch / fix

  • go code.gitea.io/gitea 1.27.0
  • go gitea.dev 1.27.0
  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260727T201416-160000.1.1

suse advisories SUSE-SU-2026:23216-1SUSE-SU-2026:23227-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260727T201416-160000.1.1

opensuse advisories openSUSE-SU-2026:21551-1

Is CVE-2026-23603 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/go-gitea/gitea/security/advisories/GHSA-x77v-q46j-393g referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go code.gitea.io/gitea
<1.27.0
1.27.0
go gitea.dev
<1.27.0
1.27.0

Affected products

  • Gitea Gitea Open Source Git Server

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.