CVE-2026-58426
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitea Actions Artifacts V4 signed URLs contain an HMAC ambiguity vulnerability that allows attackers to craft signatures valid for multiple repositories, enabling unauthorized cross-repository artifact reads and cross-task upload-state writes by bypassing the intended repository and task boundary checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Gitea installation and versionRun 'gitea --version' from the command line, or access the admin dashboard and locate the version information displayed on the diagnostics or about pageAffected if The installed Gitea version predates the patched version for CVE-2026-58426
-
Verify Actions feature is enabledInspect the Gitea configuration file (typically app.ini) and look for the [actions] section, or check if any repositories contain .gitea/workflows directories with workflow YAML filesAffected if The Actions feature is enabled in configuration or workflows are present in any repository
-
Confirm Artifacts storage is configuredReview app.ini for storage configuration sections related to artifacts, or check for the presence of artifact storage backends in the Gitea data directoryAffected if Actions Artifacts storage is configured and in use by Actions workflows
-
Review artifact access logs for anomaliesSearch Gitea logs for requests to /_actions/artifacts/ endpoints, specifically looking for access patterns involving mismatched repository identifiers or unexpected task context values in the request pathsAffected if Logs contain artifact requests where the repository or task context in the URL does not match the authenticated user's permissions
A system is vulnerable if it runs an unpatched Gitea version with Actions Artifacts feature enabled, as the HMAC signature ambiguity allows cross-repository artifact access and cross-task state manipulation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched Gitea version addressing the HMAC ambiguity in Actions Artifacts V4 signed URLs; if immediate patching is not possible, consider disabling the Actions Artifacts feature until a fix can be applied.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58426 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data