CVE-2025-69413
Gitea ≤ 1.25.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-69413 is a medium-severity Observable Response Discrepancy (CWE-204) vulnerability in Gitea. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-6 (Authentication Feedback) and SI-11 (Error Handling) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-206132
Vulnerability Data
In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V13.4.5
Mitigating Controls (NIST 800-53 r5) AI
Obscuring authentication feedback directly stops one common source of observable response discrepancies.
Error handling explicitly requires messages that avoid revealing exploitable internal information.
Information flow enforcement can block responses that would otherwise disclose internal state to unauthorized parties.
Boundary protection monitors and filters outbound responses that could leak internal state.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent introduction of inconsistent response behavior that leaks internal state.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect observable response discrepancies before deployment.
Secure coding standards explicitly require uniform error handling to prevent information leakage.
Strong authentication reduces information leakage from authentication responses.