CVE-2026-73539 Gitea CVE debrief

Who should care

Defenders responsible for Gitea deployments should assess exposure and apply patches or mitigations as needed. Users of Gitea, especially those using susceptible external renderers like pandoc, should be aware of the potential for code execution.

Why it matters

This vulnerability allows for code execution on Gitea deployments using susceptible external renderers. Defenders should prioritize verifying versions, assessing exposure, and applying patches or mitigations.

• Code execution as the Gitea service account
• Potential for unauthorized access to sensitive data
• Need for verification of Gitea versions and exposure
• Priority for applying patches or mitigations

Technical summary

The vulnerability occurs because Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style argument splitting. A crafted Context can inject additional renderer arguments, including options that load executable filter files. On deployments using a susceptible external renderer such as pandoc, a user who can place a filter file at an accessible path can cause it to execute as the Gitea service account. This can happen because the public repository markup endpoint itself can be reachable without authentication, allowing for potential code execution.

Defensive priority

Defenders should prioritize verifying the versions of Gitea in use, assessing exposure, and applying patches or mitigations as needed.

Recommended defensive actions

• Verify Gitea versions in use and assess exposure
• Apply patches or mitigations as needed
• Monitor for suspicious activity on the public repository markup endpoint
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to vendor advisories and patches. Defenders should verify Gitea versions, assess exposure, and apply patches or mitigations as needed. Evidence is limited to public sources and CVE Program records. No additional information is available beyond vendor advisories and CVE metadata.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.