Security Resilience

CVE-2025-69413

Gitea ≤ 1.25.2

Published
01 January 2026
Modified
14 October 2026
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0039 32th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS 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

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

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1110.003 Password Spraying Credential Access
Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials.
T1110.004 Credential Stuffing Credential Access
Adversaries may use credentials obtained from breach dumps of unrelated accounts to gain access to target accounts through credential overlap.
T1590 Gather Victim Network Information Reconnaissance
Adversaries may gather information about the victim's networks that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-20912Same product: Gitea Gitea
CVE-2025-68942Same product: Gitea Gitea
CVE-2025-68946Same product: Gitea Gitea
CVE-2026-89430Same product: Gitea Gitea
CVE-2023-3515Same product: Gitea Gitea
CVE-2026-103059Same product: Gitea Gitea
CVE-2026-60004Same product: Gitea Gitea
CVE-2026-20904Same product: Gitea Gitea
CVE-2026-20897Same product: Gitea Gitea
CVE-2025-68945Same product: Gitea Gitea

Affected Assets

gitea
gitea
≤ 1.25.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • 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.

PR.PS-06 full match
blocks

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.

finds

Security testing can detect observable response discrepancies before deployment.

prevents

Secure coding standards explicitly require uniform error handling to prevent information leakage.

blocks

Strong authentication reduces information leakage from authentication responses.

References