Skip to content
Noroxi
NVD / CVE Program· CNA Gitea

CVE-2026-24451: Gitea fork synchronization can expose private parent repository data

Noroxi assessment

Priority: Monitor (action score 30/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.44% (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.
  • Fixed version: code.gitea.io/gitea (Go) 1.26.3; govulncheck-vulndb (openSUSE:Leap 16.0) 0.0.20260727T201416-160000.1.1; govulncheck-vulndb (SUSE:Linux Enterprise Server 16.0) 0.0.20260727T201416-160000.1.1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to code.gitea.io/gitea (Go) 1.26.3; govulncheck-vulndb (openSUSE:Leap 16.0) 0.0.20260727T201416-160000.1.1; govulncheck-vulndb (SUSE:Linux Enterprise Server 16.0) 0.0.20260727T201416-160000.1.1 or later.

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

Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Jul 3, 2026
Updated
Oct 25, 2026
EPSS
0.4% · 39th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 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
  • A fix has been released

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

Follow CVE-2026-24451

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gitea records

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 Open Source Git Server

    • 1.26.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gocode.gitea.io/giteabefore 1.26.31.26.3
openSUSE:Leap 16.0govulncheck-vulndbbefore 0.0.20260727T201416-160000.1.10.0.20260727T201416-160000.1.1
SUSE:Linux Enterprise Server 16.0govulncheck-vulndbbefore 0.0.20260727T201416-160000.1.10.0.20260727T201416-160000.1.1

Same product

gitea: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-6886Inproper Sanitation of field leading to stored XSS
    50Plan
  • CVE-2026-20896Gitea Docker image trusts spoofable reverse-proxy headers by default
    40Plan
  • CVE-2026-56654Privilege Escalation via Access Token Scope Escalation in API
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-22555Jul 3, 2026 · Gitea organization forks can expose organization secrets without create permission
    32Monitor
  • ← EarlierCVE-2026-22874Jul 3, 2026 · Gitea webhook and migration allow-list filtering permits SSRF
    38Monitor
  • Later →CVE-2026-24690Jul 3, 2026 · Gitea pull-request branch updates use insufficient permission checks
    30Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Go:code.gitea.io/gitea1.26.3Package registry (OSV)
opensuse:govulncheck-vulndb0.0.20260727T201416-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:govulncheck-vulndb0.0.20260727T201416-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

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.

Credits

All researchers

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

Variant candidates

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

  • CVE-2026-5598241 days apartOIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
    36Monitor
  • CVE-2026-250380 days apartGitea private organization labels are visible to unauthorized users
    30Monitor
  • CVE-2026-584190 days apartNotification API leaks private issue metadata after access revocation
    30Monitor
  • CVE-2026-5842741 days apartPrivate org member list leaked via /members API endpoint — incomplete fix for PR #38145
    30Monitor
  • CVE-2026-5843441 days apartPrivate Repository Metadata Remains Accessible After Access Revocation
    30Monitor
  • CVE-2026-5844241 days apartRepository migration SSRF via multi-answer DNS allow-list bypass
    26Monitor

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • 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.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records