How severe is GHSA-ccq9-c5hv-cf64?

No CVSS score has been assigned to GHSA-ccq9-c5hv-cf64 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ccq9-c5hv-cf64?

GHSA-ccq9-c5hv-cf64 affects the following packages: gitea (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-ccq9-c5hv-cf64?

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

How do I detect GHSA-ccq9-c5hv-cf64 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-ccq9-c5hv-cf64 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-ccq9-c5hv-cf64 actively exploited in the wild?

No public exploit code has been indexed for GHSA-ccq9-c5hv-cf64 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-ccq9-c5hv-cf64?

GHSA-ccq9-c5hv-cf64 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-ccq9-c5hv-cf64?

GHSA-ccq9-c5hv-cf64 is classified as CWE-284 (CWE-284), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-ccq9-c5hv-cf64 published, and has it been updated?

GHSA-ccq9-c5hv-cf64 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

GHSA-ccq9-c5hv-cf64 — gitea

Fix: go-gitea/gitea#36341

GHSA-ccq9-c5hv-cf64 is a CWE-284 vulnerability in gitea. A fix is available for gitea — see the affected versions and patch details below.

Gitea Pull Requests Auto-Merge: Read-Only Users Can Cancel Scheduled Auto-Merge via Web Endpoint (Authorization Bypass)

Also known asCVE-2026-20888 GHSA-9cgq-wp42-4rpqGO-2026-4366

Published

Jan 30, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 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-ccq9-c5hv-cf64.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% 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 does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users.

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-ccq9-c5hv-cf64 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 HatModerate

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-ccq9-c5hv-cf64 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-ccq9-c5hv-cf64 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works