CVE-2026-104632

{"id": "CVE-2026-104632", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-104632", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-10-07T20:20:48.432483Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "affected": [{"source": "88ee5874-cf24-4952-aea0-31affedb7ff2", "affectedData": [{"vendor": "Gitea", "product": "Gitea", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "1.27.3"}], "packageName": "gitea.dev", "defaultStatus": "unaffected"}]}], "published": "2026-10-06T20:17:15.237", "references": [{"url": "https://blog.gitea.com/release-of-28.0.0/", "tags": ["Release Notes"], "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"}, {"url": "https://github.com/go-gitea/gitea/pull/39399", "tags": ["Patch"], "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"}, {"url": "https://github.com/go-gitea/gitea/releases/tag/v28.0.0", "tags": ["Release Notes"], "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"}, {"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-pvjf-7jrm-6w9g", "tags": ["Mitigation", "Vendor Advisory"], "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-285"}]}], "descriptions": [{"lang": "en", "value": "Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval."}], "lastModified": "2026-10-13T17:20:01.013", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "B7A6F93E-7785-4553-A8BB-DA84ACFF76F0", "versionEndExcluding": "28.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "88ee5874-cf24-4952-aea0-31affedb7ff2"}