Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-25712 – Information Disclosure / Organization Member Enumeration – Gitea before 1.25.5

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-25712 is a high-severity information disclosure vulnerability in Gitea, a widely deployed open-source self-hosted Git server. The flaw stems from insufficient visibility checks in Gitea’s organization permission APIs, allowing unauthenticated remote attackers to enumerate hidden organization members and access private organization details. With a CVSS v3.1 base score of 7.5 (High) and no authentication, credentials, or user interaction required, this vulnerability presents zero barrier to exploitation for any network-reachable Gitea instance.

Technical details

  • Root cause: An incorrect parameter was passed to the HasOrgOrUserVisible function in Gitea’s organization API router (routers/api/v1/org/org.go). The code used ctx.ContextUser instead of ctx.Doer when performing visibility permission checks, causing the intended access control logic to be bypassed for the requesting user.
  • Trigger conditions: Any unauthenticated network request to affected organization permission API endpoints is sufficient to trigger the information leak — no credentials, elevated privileges, or user interaction are required (PR:N, UI:N, AC:L).
  • Attack vector: Network-accessible over HTTP/HTTPS. Gitea’s REST API endpoints are exposed by design on internet-facing deployments.
  • Impact: Unauthorized disclosure of hidden organization membership and private organization structure. Exposed data can reveal internal team composition, developer identities, and organizational hierarchies to anonymous external attackers — directly facilitating targeted phishing, social engineering, and further attack planning against development infrastructure.

Affected software

  • Gitea Open Source Git Server, all versions before 1.25.5

Severity

  • CVSS v3.1 Base Score: 7.5 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Weakness: CWE-284 – Improper Access Control

Mitigation and recommended actions

  • Immediate: Upgrade to Gitea 1.25.5 (released March 16, 2026) or any later version. The fix corrects the visibility permission check in the organization API router to properly validate the identity of the requesting user.
  • If immediate patching is not feasible: Restrict network access to Gitea’s API endpoints at the firewall or reverse-proxy layer, limiting reachability to trusted networks and authenticated sources only.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge