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

CVE-2026-116289: Gitea public-only token bypass through Actions runner registration

CriticalCVSS 9.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/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.27% (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: Gitea Gitea 28.3.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Gitea Gitea 28.3.0 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 did not reject personal access tokens restricted to public resources (`public-only`) on the organization Actions runner registration-token endpoint, and the runner registered with the resulting token was not limited to public repositories. Holding only such a token with `write:organization` that belongs to an owner of a public organization, an attacker could register an organization-level runner and receive jobs of the organization's private repositories that have Actions enabled, including the workflow content, Actions secrets and variables, and a task token with access to the private repository. The issue widens what the restricted token can reach; it gives nothing beyond what the owner's full account can already do.

EUVD-2026-114794

Published: Nov 1, 2026
Updated: Nov 6, 2026
EPSS: 0.2% · 20th percentile
CWE: CWE-863

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 36 / 40 · 9.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

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.

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
- before 28.3.0affected · semver

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-113429Nov 1, 2026 · Gitea stored XSS through legacy Actions artifact Content-Encoding
21Monitor
← EarlierCVE-2026-114199Nov 1, 2026 · Gitea contribution heatmap private activity disclosure to public-only tokens
21Monitor
Later →CVE-2026-116296Nov 1, 2026 · Gitea archived repository release, milestone and label modification
26Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Gitea Gitea	28.3.0	Vendor (CNA)

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.

PublishedNov 1, 2026
Fix recordedNov 1, 2026same day
TodayNov 12, 2026+11 d

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.

https://github.com/kimc0gireporter
https://github.com/silverwindremediation developer

Variant candidates

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

CVE-2026-1176850 days apartGitea public-only package token access to private OCI blobs
36Monitor
CVE-2026-7118418 days apartGitea fork workflow approval bypass through review events
35Monitor
CVE-2026-1194410 days apartGitea public-only token bypass on bulk organization repository deletion
30Monitor
CVE-2026-7996026 days apartGitea deploy key pushes acting as the repository owner
28Monitor
CVE-2026-8668426 days apartGitea push mirror local path check uses the repository owner
28Monitor
CVE-2026-1183860 days apartGitea Actions fork workflow trust through pull request review commit
26Monitor