How severe is GHSA-8jqm-8qm3-qgqm?

No CVSS score has been assigned to GHSA-8jqm-8qm3-qgqm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8jqm-8qm3-qgqm?

GHSA-8jqm-8qm3-qgqm affects the following packages: github.com/xyproto/algernon (Go). Ecosystems affected: Go.

How do I fix GHSA-8jqm-8qm3-qgqm?

Update github.com/xyproto/algernon to 1.17.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8jqm-8qm3-qgqm is resolved across your whole dependency graph.

How do I detect GHSA-8jqm-8qm3-qgqm in my Go dependencies?

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

How do I mitigate GHSA-8jqm-8qm3-qgqm if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-8jqm-8qm3-qgqm actively exploited in the wild?

No public exploit code has been indexed for GHSA-8jqm-8qm3-qgqm 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-8jqm-8qm3-qgqm?

GHSA-8jqm-8qm3-qgqm has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-8jqm-8qm3-qgqm?

GHSA-8jqm-8qm3-qgqm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-8jqm-8qm3-qgqm published, and has it been updated?

GHSA-8jqm-8qm3-qgqm was published on December 10, 2025 and was last updated on December 18, 2025. 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

Algernon Cross-Site Scripting vulnerabilityGHSA-8jqm-8qm3-qgqm

Fix: xyproto/algernon@cd88320

GHSA-8jqm-8qm3-qgqm is a Cross-site Scripting (XSS) vulnerability in github.com/xyproto/algernon. A fix is available for github.com/xyproto/algernon — see the affected versions and patch details below.

Also known asCVE-2025-65754GO-2025-4228

Published

Dec 10, 2025

Updated

Dec 18, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8jqm-8qm3-qgqm.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs41th percentile — riskier than 41% 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/xyproto/algernon

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

Cross-site Scripting vulnerability in Algernon v1.17.4 allows attackers to execute arbitrary code via injecting a crafted payload into a filename.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/xyproto/algernon`	all versions	1.17.5`go get github.com/xyproto/algernon@v1.17.5`

Affected Products

1 product · 1 configurations

Application

algernonalgernon_project

1 version

1.17.4

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/xyproto/algernon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/xyproto/algernon to 1.17.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8jqm-8qm3-qgqm is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Cross-site Scripting vulnerability in Algernon v1.17.4 allows attackers to execute arbitrary code via injecting a crafted payload into a filename.

O3 Security · Impact-Aware SCA

Is GHSA-8jqm-8qm3-qgqm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works