How severe is GHSA-x2xw-hw8g-6773?

No CVSS score has been assigned to GHSA-x2xw-hw8g-6773 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x2xw-hw8g-6773?

GHSA-x2xw-hw8g-6773 affects the following packages: govuk_tech_docs (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-x2xw-hw8g-6773?

Update govuk_tech_docs to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2xw-hw8g-6773 is resolved across your whole dependency graph.

How do I detect GHSA-x2xw-hw8g-6773 in my RubyGems dependencies?

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

How do I mitigate GHSA-x2xw-hw8g-6773 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-x2xw-hw8g-6773 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x2xw-hw8g-6773 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-x2xw-hw8g-6773?

GHSA-x2xw-hw8g-6773 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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-x2xw-hw8g-6773?

GHSA-x2xw-hw8g-6773 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-x2xw-hw8g-6773 published, and has it been updated?

GHSA-x2xw-hw8g-6773 was published on April 11, 2023 and was last updated on July 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.

💎 RubyGems

Not in CISA KEV

govuk_tech_docs vulnerable to unescaped HTML on search results pageGHSA-x2xw-hw8g-6773

Fix: alphagov/tech-docs-gem#323

GHSA-x2xw-hw8g-6773 is a Cross-site Scripting (XSS) vulnerability in govuk_tech_docs. A fix is available for govuk_tech_docs — see the affected versions and patch details below.

Also known asCVE-2024-22048

Published

Apr 11, 2023

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 27, 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-x2xw-hw8g-6773.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎govuk_tech_docs

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

Description

Impact

Pages that are indexed in search results have their entire contents indexed, including any HTML code snippets. These HTML snippets would appear in the search results unsanitised, so it was possible to render arbitrary HTML or run arbitrary scripts.

This is a low risk security issue; to exploit it, an attacker would need to find a way of committing malicious code to a page indexed by a site that uses tech-docs-gem (which are typically not editable by untrusted users). Their code would also be limited by the relatively short length that's rendered in the corresponding search result. Nevertheless, the XSS would then be triggerable by visiting a pre-constructed URL (/search/index.html?q=some+search+term), which users could be tricked into clicking on through social engineering.

Patches

This has been fixed in v3.3.1. HTML is now sanitised in search results.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`govuk_tech_docs`	≥ 2.0.2&&< 3.3.1	3.3.1`bundle update govuk_tech_docs --conservative`

Affected Products

1 product · 1 configurations

Application

govuk tech docsgov.uk

≥ 2.0.2 && < 3.3.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for govuk_tech_docs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update govuk_tech_docs to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2xw-hw8g-6773 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

### Impact Pages that are indexed in search results have their entire contents indexed, including any HTML code snippets. These HTML snippets would appear in the search results unsanitised, so it was possible to render arbitrary HTML or run arbitrary scripts. This is a low risk security issue; to exploit it, an attacker would need to find a way of committing malicious code to a page indexed by a site that uses tech-docs-gem (which are typically not editable by untrusted users). Their code would also be limited by the relatively short length that's rendered in the corresponding search result.

O3 Security · Impact-Aware SCA

Is GHSA-x2xw-hw8g-6773 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works