How severe is GHSA-f4wq-6ww5-m56p?

No CVSS score has been assigned to GHSA-f4wq-6ww5-m56p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f4wq-6ww5-m56p?

GHSA-f4wq-6ww5-m56p affects the following packages: gitea (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-f4wq-6ww5-m56p?

Update gitea to 1.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4wq-6ww5-m56p is resolved across your whole dependency graph.

How do I detect GHSA-f4wq-6ww5-m56p in my Bitnami dependencies?

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

How do I mitigate GHSA-f4wq-6ww5-m56p if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-f4wq-6ww5-m56p actively exploited in the wild?

No public exploit code has been indexed for GHSA-f4wq-6ww5-m56p 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-f4wq-6ww5-m56p?

GHSA-f4wq-6ww5-m56p has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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-f4wq-6ww5-m56p?

GHSA-f4wq-6ww5-m56p is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f4wq-6ww5-m56p published, and has it been updated?

GHSA-f4wq-6ww5-m56p was published on January 30, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

Gitea Release Email Notifications Leak Private Repository Release Details After Access RevocationGHSA-f4wq-6ww5-m56p

Fix: go-gitea/gitea#36319

GHSA-f4wq-6ww5-m56p is a CWE-284 vulnerability in gitea. A fix is available for gitea — see the affected versions and patch details below.

Also known asCVE-2026-0798 GHSA-8fwc-qjw5-rvgpGO-2026-4365

Published

Jan 30, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 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-f4wq-6ww5-m56p.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

📦gitea

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

Description

Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`gitea`	all versions	1.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 gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gitea to 1.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4wq-6ww5-m56p is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-f4wq-6ww5-m56p (CC BY 4.0)