CVE•Published 2026-10-06•Modified 2026-10-15•0 articles on news•4 live references•NVD data

CVE-2026-103670Gitea · Gitea

Vulnerability data via NVD (ingested)

CVSS v3.1

7.5

HIGH

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

EPSS percentile

Exploit Prediction Scoring System · top 89% of all CVEs

Weaknesses (CWE)

CWE-667Improper Locking

Description

When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.

Timeline

Published 2026-10-06

Modified 2026-10-15

External references

NVD MITRE GitHub PoC VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag3,562 hosts

vuln:CVE-2026-103670

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Gitea Gitea"

All exposed Gitea Gitea instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Gitea"

HTTP body or banner mentions "Gitea" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2026-103670