How severe is CVE-2022-24773?

CVE-2022-24773 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-24773?

CVE-2022-24773 affects the following packages: node-forge (npm). Ecosystems affected: npm.

How do I fix CVE-2022-24773?

Update node-forge to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24773 is resolved across your whole dependency graph.

How do I detect CVE-2022-24773 in my npm dependencies?

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

How do I mitigate CVE-2022-24773 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 CVE-2022-24773 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24773 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 CVE-2022-24773?

CVE-2022-24773 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th 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 CVE-2022-24773?

CVE-2022-24773 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24773 published, and has it been updated?

CVE-2022-24773 was published on March 18, 2022 and was last updated on October 28, 2026. 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

MEDIUM severity

CVE-2022-24773 — node-forge

MEDIUMFix: digitalbazaar/forge@3f0b49a

CVE-2022-24773 is a medium-severity (CVSS 5.3) CWE-347 vulnerability in node-forge. A fix is available for node-forge — see the affected versions and patch details below.

Improper Verification of Cryptographic Signature in `node-forge`

Also known asGHSA-2r2c-g63r-vccr

Published

Mar 18, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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.

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

node-forgenpm

55.5Mdownloads / week

Description

Impact

RSA PKCS#1 v1.5 signature verification code is not properly checking DigestInfo for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest.

Patches

The issue has been addressed in node-forge 1.3.0.

For more information

If you have any questions or comments about this advisory:

Open an issue in forge
Email us at example email address

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-forge`	all versions	1.3.0`npm install node-forge@1.3.0`

Affected Products

1 product · 1 configurations

Application

forgedigitalbazaar

< 1.3.0

range

Detection & mitigation playbook

Open-source dependency

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

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

Product	Fixed in	Advisory
OpenShift Service Mesh 2.1	`openshift-service-mesh/kiali-rhel8:1.36.9-1`	RHSA-2022:1739
Red Hat OpenShift Data Foundation 4.11 on RHEL8	`odf4/mcg-core-rhel8:v4.11.0-30`	RHSA-2022:6156
RHINT Service Registry 2.3.0 GA	`node-forge`	RHSA-2022:6835

Frequently Asked Questions

### Impact RSA PKCS#1 v1.5 signature verification code is not properly checking `DigestInfo` for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest. ### Patches The issue has been addressed in `node-forge` `1.3.0`. ### For more information If you have any questions or comments about this advisory: * Open an issue in [forge](https://github.com/digitalbazaar/forge) * Email us at [example email address](mailto:[email protected])

O3 Security · Impact-Aware SCA

Is CVE-2022-24773 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CWE Classification

CWE-347CWE-347

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

forge

6.1/10

Code-Review0/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

Disclosed

Mar 18, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-24773

GHSA-2r2c-g63r-vccr

References

Advisorygithub.com · CVE 2022 24773.json Advisorygithub.com · GHSA 2r2c g63r vccr Advisorynvd.nist.gov · CVE 2022 24773 Fixgithub.com · 3f0b49a0573ef1bb7af7f5673c0cfebf00424df1 Fixgithub.com · bb822c02df0b61211836472e29b9790cc541cdb2 Packagegithub.com · forge

Related vulnerabilities

This CVE is medium severity; 6 of 8 other CVEs affecting node-forge are rated as high or higher (top: high).

CVE-2026-118780CVE-2026-118775CVE-2026-118778CVE-2026-119186CVE-2026-119190CVE-2026-118777CVE-2026-118779CVE-2026-119188

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-24773 — node-forge

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

For more information

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-24773 in your dependencies?