How severe is GHSA-c27r-x354-4m68?

No CVSS score has been assigned to GHSA-c27r-x354-4m68 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c27r-x354-4m68?

GHSA-c27r-x354-4m68 affects the following packages: xml-crypto (npm). Ecosystems affected: npm.

How do I fix GHSA-c27r-x354-4m68?

Update xml-crypto to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c27r-x354-4m68 is resolved across your whole dependency graph.

How do I detect GHSA-c27r-x354-4m68 in my npm dependencies?

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

How do I mitigate GHSA-c27r-x354-4m68 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-c27r-x354-4m68 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c27r-x354-4m68 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.

When was GHSA-c27r-x354-4m68 published, and has it been updated?

GHSA-c27r-x354-4m68 was published on October 27, 2020 and was last updated on August 2, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

xml-crypto's HMAC-SHA1 signatures can bypass validation via key confusionGHSA-c27r-x354-4m68

Fix: yaronn/xml-crypto@3d9db71

GHSA-c27r-x354-4m68 is a security vulnerability in xml-crypto. A fix is available for xml-crypto — see the affected versions and patch details below.

Published

Oct 27, 2020

Updated

Aug 2, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 2, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

547other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

xml-cryptonpm

7.8Mdownloads / week

Description

Impact

An attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation.

Patches

Version 2.0.0 has the fix.

Workarounds

The recommendation is to upgrade. In case that is not possible remove the 'http://www.w3.org/2000/09/xmldsig#hmac-sha1' entry from SignedXml.SignatureAlgorithms.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`xml-crypto`	all versions	2.0.0`npm install xml-crypto@2.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xml-crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xml-crypto to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c27r-x354-4m68 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact An attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation. ### Patches Version 2.0.0 has the fix. ### Workarounds The recommendation is to upgrade. In case that is not possible remove the 'http://www.w3.org/2000/09/xmldsig#hmac-sha1' entry from SignedXml.SignatureAlgorithms.

O3 Security · Impact-Aware SCA

Is GHSA-c27r-x354-4m68 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works