CVE-2026-25946· CVE.org (no NVD analysis yet)· CNA Gitea

Gitea OpenID discovery server-side request forgery

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
No fixed version is recorded, but the references include a patch (commit or PR) link.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

When OpenID sign-in is enabled, Gitea accepts a user-supplied OpenID URL and performs discovery requests without validating the destination against internal network addresses. An unauthenticated remote attacker can cause the server to contact loopback or private-network HTTP services. This can expose internal service behavior and enable interaction with resources that are not directly reachable by the attacker.

MediumCVSS 5.3 · v3.1—No exploit No fix recorded

EUVD-2026-101279

Published: Oct 14, 2026
Updated: Oct 14, 2026
EPSS: 0.4% · 33th percentile
CWE: CWE-918

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Gitea). Independent of NVD's CPE analysis and usually ahead of it.

Gitea Gitea
- 1.25.4affected

Same product

gitea: all records

Other highest-scoring records for the same primary product.

CVE-2026-60004Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.KEV
76This week
CVE-2026-59774Gitea Org-mode file disclosure and code execution
60This week
CVE-2022-30781Gitea before 1.16.7 does not escape git fetch remote.
60This week

Published before and after this one in the same product

← EarlierCVE-2026-97208Oct 6, 2026 · Gitea push mirror API bypass of DISABLE_NEW_PUSH policy
19Monitor
← EarlierCVE-2026-97626Oct 6, 2026 · Gitea profile feed disclosure bypassing user visibility
17Monitor
Later →CVE-2026-59766Oct 14, 2026 · Gitea private repository metadata disclosure after access revocation
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

go-gitea/giteaPR 36729

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

https://github.com/DhiyaneshGeekreporter
https://github.com/neo-ai-engineerreporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-3496670 days apartGitea prior to 1.27.0 SSRF via Migration URI Fetch Bypass
33Monitor
CVE-2026-1046368 days apartGitea SSRF through Git HTTP redirects in mirrors and fetches
30Monitor
CVE-2026-703578 days apartGitea repository migration SSRF through DNS rebinding
30Monitor
CVE-2026-782310 days apartGitea blind SSRF through OpenID assertion verification
21Monitor
CVE-2026-964008 days apartGitea migration SSRF to reserved addresses through ALLOWED_DOMAINS
17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).