Skip to content
Fencer Intel
medium 5.3

CVE-2025-69413 json

Gitea's /api/v1/user endpoint has different responses for failed authentication depending on whether a username exists

published 10mo ago modified 26d ago also BIT-gitea-2025-69413 , EUVD-2025-206132 , GHSA-pc73-rj2c-wvf9 , GO-2026-4274

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

Summary

In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.

Patch / fix

  • go code.gitea.io/gitea 1.25.2
  • bitnami gitea 1.25.2
  • Gitea Gitea 1.25.2
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260114T191543-150000.1.137.1

suse advisories SUSE-SU-2026:0142-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2025-69413 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-69413 updated cvss 5.3

Gitea: Gitea: Information disclosure via differing authentication responses

  • Red Hat OpenShift Pipelines openshift-pipelines/pipelines-pipelines-as-code-cli-rhel8, openshift-pipelines/pipelines-pipelines-as-code-cli-rhel9, openshift-pipelines/pipelines-pipelines-as-code-watcher-rhel8, openshift-pipelines/pipelines-pipelines-as-code-watcher-rhel9, openshift-pipelines/pipelines-pipelines-as-code-webhook-rhel8, openshift-pipelines/pipelines-pipelines-as-code-webhook-rhel9, +2 more
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
10mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go code.gitea.io/gitea
<1.25.2
1.25.2
bitnami gitea
<1.25.2
1.25.2

Affected products

  • Gitea Gitea

Classification

Weakness
  • CWE-204 Observable Response Discrepancy

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.