How severe is GHSA-2vgv-hgv4-22mh?

No CVSS score has been assigned to GHSA-2vgv-hgv4-22mh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2vgv-hgv4-22mh?

GHSA-2vgv-hgv4-22mh affects the following packages: github.com/go-gitea/gitea (Go). Ecosystems affected: Go.

How do I fix GHSA-2vgv-hgv4-22mh?

Update github.com/go-gitea/gitea to 1.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vgv-hgv4-22mh is resolved across your whole dependency graph.

How do I detect GHSA-2vgv-hgv4-22mh in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-gitea/gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2vgv-hgv4-22mh if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-2vgv-hgv4-22mh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2vgv-hgv4-22mh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2vgv-hgv4-22mh?

GHSA-2vgv-hgv4-22mh has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2vgv-hgv4-22mh?

GHSA-2vgv-hgv4-22mh is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2vgv-hgv4-22mh published, and has it been updated?

GHSA-2vgv-hgv4-22mh was published on January 23, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Gitea improperly exposes issue and pull request titlesGHSA-2vgv-hgv4-22mh

Fix: go-gitea/gitea#36339

GHSA-2vgv-hgv4-22mh is a Information Exposure vulnerability in github.com/go-gitea/gitea. A fix is available for github.com/go-gitea/gitea — see the affected versions and patch details below.

Also known asBIT-gitea-2026-20800CVE-2026-20800 GHSA-g54m-9f6g-wj7qGO-2026-4362

Published

Jan 23, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2vgv-hgv4-22mh.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/go-gitea/gitea

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/go-gitea/gitea`	all versions	1.25.4`go get github.com/go-gitea/gitea@v1.25.4`

Affected Products

1 product · 1 configurations

Application

giteagitea

< 1.25.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-gitea/gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/go-gitea/gitea to 1.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vgv-hgv4-22mh is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-2vgv-hgv4-22mh in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works