CVE-2026-68964 Gitea CVE debrief

Who should care

Defenders responsible for Gitea systems, especially those using versions prior to 1.27.3, should assess exposure and potential impact. This includes Gitea administrators, security teams, and operators who manage Gitea deployments. They should verify exposure, assess impact, and consider applying patches or updates to mitigate the vulnerability.

Why it matters

This vulnerability may lead to metadata disclosure for restricted users in Gitea systems. Defenders should verify exposure, assess impact, and consider applying patches or updates.

• Potential metadata disclosure for restricted users
• Need to verify exposure and assess impact on systems using Gitea
• Possible need for patching or updates to Gitea

Technical summary

Gitea's user SSH and GPG key-list API endpoints omit the profile visibility check applied by their web equivalents. A restricted account can retrieve public keys, key titles, fingerprints, and GPG-embedded email addresses belonging to Limited-visibility users. The vulnerability affects Gitea versions prior to 1.27.3. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if they use Gitea versions prior to 1.27.3. The disclosure concerns public key material and associated metadata, not private cryptographic keys.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if they use Gitea versions prior to 1.27.3.

Recommended defensive actions

• Verify Gitea version and check if it's prior to 1.27.3
• Assess exposure and potential impact on systems using Gitea
• Apply patches or updates to Gitea if available
• 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 about the vulnerability, including its description and affected versions. However, the CVSS score and severity are not provided. The vulnerability was published on 2026-10-14T14:36:28.026Z and has not been modified since then. The source item and CVE record offer limited information on the vulnerability's impact and affected systems. Defenders should verify exposure and assess impact based on available data.

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.