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:NSummary
CVE-2025-69413 is a medium-severity Observable Response Discrepancy (CWE-204) vulnerability in Gitea Gitea. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Account Discovery (T1087); ranked at the 28th 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 TechniquesAI
Why these techniques?
Observable response discrepancy on /api/v1/user directly enables username enumeration for account discovery (T1087).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires error messages to avoid revealing information (such as username existence) that could be exploited by adversaries.
Requires obscuring authentication feedback so that failed login responses do not differ based on whether an identifier exists.
Enforces uniform access decision responses, preventing observable discrepancies that leak account existence on the /api/v1/user endpoint.
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.
Network security controls can enforce uniform responses and suppress observable discrepancies.
Secure SDLC practices include error-handling and response standardization to avoid information disclosure.
Application security requirements typically mandate consistent, non-revealing error messages.
Secure architecture principles discourage designs that leak internal state via differing responses.
Secure coding standards explicitly require uniform error handling to prevent information leakage.