CVE-2024-23337VulnerabilityPublished 8 Jul 2025Updated 21 Aug 2026

Red Hat Security Advisory: jq security update

Affects Red Hat jqSource GCVE Database

Mentioned vulnerabilities

CVE-2025-48060

Not known to be exploited.

Data as of 26 Oct 2026, 09:15 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released an official security update for jq in Red Hat Enterprise Linux 9.2 (package version 1.6-15.el9_2.2) that addresses these vulnerabilities. Users should apply this update promptly following Red Hat's published guidance at https://access.redhat.com/articles/11258. No additional mitigation steps are indicated or required beyond applying the official patch.

Description

Red Hat has issued a security advisory for jq, a command-line JSON processor, addressing two vulnerabilities: a signed integer overflow (CVE-2024-23337) and a stack-buffer-overflow detected by AddressSanitizer (CVE-2025-48060). These vulnerabilities affect jq as packaged in Red Hat Enterprise Linux 9.2 and related distributions. The security impact is rated as moderate by Red Hat. Updates are available to fix these issues in the jq package version 1.6-15.el9_2.2. Users of affected Red Hat Enterprise Linux 9.2 systems should apply the provided update to mitigate these vulnerabilities.

Impact

The vulnerabilities could allow an attacker to cause memory corruption through integer overflow or buffer overflow conditions when processing JSON data with jq. This may lead to application crashes or potentially other unintended behavior. Red Hat rates the security impact as moderate. There are no known exploits in the wild reported at this time.

Summary

The jq utility, used for processing JSON data on the command line, contains two security flaws: a signed integer overflow in the function jvp_array_write (CVE-2024-23337) and a stack-buffer-overflow identified in jq_fuzz_execute (jv_string_vfmt) (CVE-2025-48060). Both vulnerabilities could potentially lead to memory corruption issues. Red Hat has released an update for jq in Red Hat Enterprise Linux 9.2 to address these flaws. The advisory references the Red Hat Security Advisory RHSA-2025:10615 and provides updated packages for multiple architectures. No CVSS scores are provided in the advisory, but the impact is assessed as moderate.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-126Buffer Over-read (opens in a new tab)
Variant weakness
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 21 Aug 2026, 16:15 UTC

WeaknessesCWE-190, CWE-126

Technical details

References

Community reviews

Related threats