How severe is GHSA-hjp3-5g2q-7jww?

GHSA-hjp3-5g2q-7jww has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hjp3-5g2q-7jww?

GHSA-hjp3-5g2q-7jww affects the following packages: audited (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-hjp3-5g2q-7jww?

Update audited to 5.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hjp3-5g2q-7jww is resolved across your whole dependency graph.

How do I detect GHSA-hjp3-5g2q-7jww in my RubyGems dependencies?

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

How do I mitigate GHSA-hjp3-5g2q-7jww 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.

How does O3 Security protect against GHSA-hjp3-5g2q-7jww?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hjp3-5g2q-7jww can be triaged on real exposure rather than presence alone.

Is GHSA-hjp3-5g2q-7jww actively exploited in the wild?

No public exploit code has been indexed for GHSA-hjp3-5g2q-7jww 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-hjp3-5g2q-7jww?

GHSA-hjp3-5g2q-7jww has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th 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.

When was GHSA-hjp3-5g2q-7jww published, and has it been updated?

GHSA-hjp3-5g2q-7jww was published on May 1, 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

LOW severity

GHSA-hjp3-5g2q-7jww — audited

LOWFix: collectiveidea/audited#669

GHSA-hjp3-5g2q-7jww is a low-severity (CVSS 3.1) vulnerability in audited. A fix is available for audited — see the affected versions and patch details below.

Race Condition leading to logging errors

Also known asCVE-2024-22047

Published

May 1, 2023

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, 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-hjp3-5g2q-7jww.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-hjp3-5g2q-7jww plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

💎audited

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

In certain setups with threaded web servers, Audited's use of Thread.current can incorrectly attributed audits to the wrong user.

Fixed in 5.3.3.

In March, @convisoappsec noticed that the library in question had a Race Condition problem, which caused logs to be registered at times with different users than those who performed the genuine actions.

The first issue we identified was from November 2021: https://github.com/collectiveidea/audited/issues/601
So the solution was implemented in the following Pull Request: https://github.com/collectiveidea/audited/pull/669
And the feature was published in version 5.3.3: RELEASE: https://github.com/collectiveidea/audited/pull/671

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`audited`	≥ 4.0.0&&< 5.3.3	5.3.3`bundle update audited --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for audited, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update audited to 5.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hjp3-5g2q-7jww 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hjp3-5g2q-7jww can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hjp3-5g2q-7jww. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatLow

Product	Fixed in	Advisory
Red Hat Satellite 6.15 for RHEL 8	`rubygem-audited-0:5.4.2-1.el8sat`	RHSA-2024:2010

Frequently Asked Questions

In certain setups with threaded web servers, Audited's use of `Thread.current` can incorrectly attributed audits to the wrong user. Fixed in 5.3.3. In March, @convisoappsec noticed that the library in question had a Race Condition problem, which caused logs to be registered at times with different users than those who performed the genuine actions. - The first issue we identified was from November 2021: https://github.com/collectiveidea/audited/issues/601 - So the solution was implemented in the following Pull Request: https://github.com/collectiveidea/audited/pull/669 - And the feature

O3 Security · Impact-Aware SCA

Is GHSA-hjp3-5g2q-7jww in your dependencies?

O3 Security finds GHSA-hjp3-5g2q-7jww across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works