CVE-2026-71301 Gitea CVE debrief

Who should care

Defenders managing Gitea instances, especially those with finely tuned repository permissions, should assess exposure to unauthorized pull request metadata access. This includes reviewing the instance configuration, restricting access to markup preview requests, and monitoring for unauthorized access to pull request metadata. Additionally, defenders should prioritize verifying exposure of Gitea instances to unauthorized pull request metadata access, and

Why it matters

Defenders should prioritize verifying exposure of Gitea instances to unauthorized pull request metadata access, especially in environments where repository permissions are finely tuned.

• Potential unauthorized access to private pull request metadata.
• Bypassing of repository permissions for Issues and Pull Requests access.

Technical summary

Gitea's repository markup endpoint resolves same-repository pull request references without enforcing the viewer's Pull Requests permission. A member with only Wiki access to a private repository can submit a markup preview request and retrieve a private pull request's title and state icon despite lacking Issues and Pull Requests access. This vulnerability allows unauthorized access to pull request metadata, potentially bypassing repository permissions for Issues and Pull Requests access. Defenders should prioritize verifying exposure of Gitea instances to unauthorized pull request metadata access, especially in environments where repository permissions are finely tuned.

Defensive priority

Defenders should prioritize verifying exposure of Gitea instances to unauthorized pull request metadata access, especially in environments where repository permissions are finely tuned.

Recommended defensive actions

• Verify Gitea instance configuration to ensure proper enforcement of repository permissions.
• Restrict access to markup preview requests to authorized personnel.
• Monitor for unauthorized access to pull request metadata.
• 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 Program record and NVD vulnerability detail provide official information about the vulnerability. Gitea's repository markup endpoint resolves same-repository pull request references without enforcing the viewer's Pull Requests permission.

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.