How severe is GHSA-8hfj-j24r-96c4?

GHSA-8hfj-j24r-96c4 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8hfj-j24r-96c4?

GHSA-8hfj-j24r-96c4 affects the following packages: moment (npm), Moment.js (NuGet). Ecosystems affected: npm, NuGet.

How do I fix GHSA-8hfj-j24r-96c4?

Update moment to 2.29.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hfj-j24r-96c4 is resolved across your whole dependency graph.

How do I detect GHSA-8hfj-j24r-96c4 in my npm, NuGet dependencies?

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

How do I mitigate GHSA-8hfj-j24r-96c4 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-8hfj-j24r-96c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8hfj-j24r-96c4 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-8hfj-j24r-96c4?

GHSA-8hfj-j24r-96c4 has an EPSS (Exploit Prediction Scoring System) score of 13.9%, placing it in the 97th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-8hfj-j24r-96c4?

GHSA-8hfj-j24r-96c4 is classified as Path Traversal (CWE-22), CWE-27 (CWE-27). These weakness types 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-8hfj-j24r-96c4 published, and has it been updated?

GHSA-8hfj-j24r-96c4 was published on April 4, 2022 and was last updated on September 10, 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.NET NuGet

Not in CISA KEV

HIGH severity

Path Traversal: 'dir/../../filename' in moment.localeGHSA-8hfj-j24r-96c4

HIGHFix: moment/moment@4211bfc

GHSA-8hfj-j24r-96c4 is a high-severity (CVSS 7.5) Path Traversal vulnerability in moment. EPSS puts its 30-day exploitation probability at 13.9% (97th percentile). A fix is available for moment — see the affected versions and patch details below.

Also known asCVE-2022-24785

Published

Apr 4, 2022

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-8hfj-j24r-96c4.

EPSS Exploitation Probability

via FIRST.org ↗

13.9%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-8hfj-j24r-96c4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs 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.

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

momentnpm

22.6Mdownloads / week

Description

Impact

This vulnerability impacts npm (server) users of moment.js, especially if user provided locale string, eg fr is directly used to switch moment locale.

Patches

This problem is patched in 2.29.2, and the patch can be applied to all affected versions (from 1.0.1 up until 2.29.1, inclusive).

Workarounds

Sanitize user-provided locale name before passing it to moment.js.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Open an issue in moment repo

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`moment`	all versions	2.29.2`npm install moment@2.29.2`
.NETNuGet	`Moment.js`	all versions	2.29.2`dotnet add package Moment.js --version 2.29.2`

Affected Products

5 products · 7 configurations

debian linuxdebian

1 version

10.0

fedorafedoraproject

2 versions

3536

Application

momentmomentjs

≥ 1.0.1 && < 2.29.2

range

Application

active iqnetapp

all

Application

tenable.sctenable

< 5.21.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 moment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moment to 2.29.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hfj-j24r-96c4 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

In Quay 3.10 and above, no version of affected momentjs is present.

Workaround published by Red Hat

Sanitize the user-provided locale name before passing it to Moment.js.

Source: Red Hat security advisory for GHSA-8hfj-j24r-96c4 (CC BY 4.0)

Product	Fixed in	Advisory
OpenShift Service Mesh 2.0	`servicemesh-prometheus-0:2.14.0-18.el8.1`	RHSA-2022:6272
OpenShift Service Mesh 2.1	`openshift-service-mesh/kiali-rhel8:1.36.10-2`	RHSA-2022:5006
OpenShift Service Mesh 2.1	`servicemesh-prometheus-0:2.23.0-9.el8`	RHSA-2022:6277
Red Hat Ceph Storage 5.3	`ceph-2:16.2.10-94.el8cp`	RHSA-2023:0076
Red Hat Ceph Storage 6.1	`rhceph/rhceph-6-dashboard-rhel9:6-75`	RHSA-2023:3642
Red Hat Fuse 7.11.1	`Moment.js`	RHSA-2022:8652
Red Hat Fuse 7.12	see advisory	RHSA-2023:3954
Red Hat JBoss Enterprise Application Platform	`org.jboss.hal/hal-console:3.3.12.Final-redhat-00001`	RHSA-2022:4922

Frequently Asked Questions

### Impact This vulnerability impacts npm (server) users of moment.js, especially if user provided locale string, eg `fr` is directly used to switch moment locale. ### Patches This problem is patched in 2.29.2, and the patch can be applied to all affected versions (from 1.0.1 up until 2.29.1, inclusive). ### Workarounds Sanitize user-provided locale name before passing it to moment.js. ### References _Are there any links users can visit to find out more?_ ### For more information If you have any questions or comments about this advisory: * Open an issue in [moment repo](https://github.com/