Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 0.17% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-49839High confidence
jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow
jqlang · jq
Official source article: GitHub GHSA-CFH2-VWFQ-QFMM ↗. Check the applicable product and release in the original source.
7.1HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs jqlang jq and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | jq | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.8.2-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | jq | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.8.2-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | jq | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.7.1-6+deb13u3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | jq | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.6-2.1+deb12u2 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | jq | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.8.1-8 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | jq | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.8.1-8 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | jq | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-49839 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjq: jq: Heap out-of-bounds write via oversized raw file processing
The vendor explicitly identifies these products as affected by this CVE.
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-27/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
- automation-controller.src as a component of Red Hat Ansible Automation Platform 2
- jq.src as a component of Red Hat Ceph Storage 4
- jq as a component of Red Hat Enterprise Linux 10
- jq-devel as a component of Red Hat Enterprise Linux 10
- jq.src as a component of Red Hat Enterprise Linux 10
- jq as a component of Red Hat Enterprise Linux 8
- jq-devel as a component of Red Hat Enterprise Linux 8
- jq.src as a component of Red Hat Enterprise Linux 8
- Summary
- A flaw was found in jq, a command-line JSON processor. This vulnerability allows an attacker to trigger a heap out-of-bounds write by providing a specially crafted, oversized file to the `jq --rawfile` option. This can lead to a denial of service (DoS), making the affected system or application unavailable, and may also impact data integrity. Exploitation requires user interaction, as a user must process the malicious file.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` can turn a handled oversized-string error into invalid-state reuse and a real heap out-of-bounds write in assertion-disabled builds. When jv_load_file(raw=1) reads an attacker-controlled file, it repeatedly appends file chunks to the same jv string accumulator. Once jv_string_append_buf() returns jv_invalid_with_msg("String too long"), the raw-file loop does not stop. If the file contains at least one more byte, the next loop iteration appends a new chunk to an object that is already invalid. With assertions enabled this aborts in jvp_string_ptr(). With assertions disabled, the invalid object is interpreted as a string object and ASan reports heap-buffer-overflow. This vulnerability is fixed in 1.8.2.
What
jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` can turn a handled oversized-string error into invalid-state reuse and a real heap out-of-bounds write in assertion-disabled builds. When jv_load_file(raw=1) reads an attacker-controlled file, it repeatedly appends file chunks to the same jv string accumulator. Once jv_string_append_buf() returns jv_invalid_with_msg("String too long"), the raw-file loop does not stop. If the file contains at least one more byte, the next loop iteration appends a new chunk to an object that is already invalid. With assertions enabled this aborts in jvp_string_ptr(). With assertions disabled, the invalid object is interpreted as a string object and ASan reports heap-buffer-overflow. This vulnerability is fixed in 1.8.2.
Why
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` can turn a handled oversized-string error into invalid-state reuse and a real heap out-of-bounds write in assertion-disabled builds. When jv_load_file(raw=1) reads an attacker-controlled file, it repeatedly appends file chunks to the same jv string accumulator. Once jv_string_append_buf() returns jv_invalid_with_msg("String too long"), the raw-file loop does not stop. If the file contains at least one more byte, the next loop iteration appends a new chunk to an object that is already invalid. With assertions enabled this aborts in jvp_string_ptr(). With assertions disabled, the invalid object is interpreted as a string object and ASan reports heap-buffer-overflow. This vulnerability is fixed in 1.8.2.
Why
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- local access → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-787 ↗
CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-27/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
- automation-controller.src as a component of Red Hat Ansible Automation Platform 2
- jq.src as a component of Red Hat Ceph Storage 4
- jq as a component of Red Hat Enterprise Linux 10
- jq-devel as a component of Red Hat Enterprise Linux 10
- jq.src as a component of Red Hat Enterprise Linux 10
- jq as a component of Red Hat Enterprise Linux 8
- jq-devel as a component of Red Hat Enterprise Linux 8
- jq.src as a component of Red Hat Enterprise Linux 8
- jq as a component of Red Hat Enterprise Linux 9
- jq-devel as a component of Red Hat Enterprise Linux 9
- jq.src as a component of Red Hat Enterprise Linux 9
- openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
- openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
- Fixed
- Action
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 25 Jun 2026 · Last source change 25 Jun 2026, 17:55 UTC · CWE-787 · Out-of-bounds Write
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-39500
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 1.8.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- < 1.8.2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; automation-controller.src as a component of Red Hat Ansible Automation Platform 2; jq.src as a component of Red Hat Ceph Storage 4; jq as a component of Red Hat Enterprise Linux 10; jq-devel as a component of Red Hat Enterprise Linux 10; jq.src as a component of Red Hat Enterprise Linux 10; jq as a component of Red Hat Enterprise Linux 8; jq-devel as a component of Red Hat Enterprise Linux 8; jq.src as a component of Red Hat Enterprise Linux 8; jq as a component of Red Hat Enterprise Linux 9; jq-devel as a component of Red Hat Enterprise Linux 9; jq.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: jq-main@aarch64 as a component of Red Hat Hardened Images; jq-main@src as a component of Red Hat Hardened Images; jq-main@x86_64 as a component of Red Hat Hardened Images
- After
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; automation-controller.src as a component of Red Hat Ansible Automation Platform 2; jq.src as a component of Red Hat Ceph Storage 4; jq as a component of Red Hat Enterprise Linux 10; jq-devel as a component of Red Hat Enterprise Linux 10; jq.src as a component of Red Hat Enterprise Linux 10; jq as a component of Red Hat Enterprise Linux 8; jq-devel as a component of Red Hat Enterprise Linux 8; jq.src as a component of Red Hat Enterprise Linux 8; jq as a component of Red Hat Enterprise Linux 9; jq-devel as a component of Red Hat Enterprise Linux 9; jq.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: jq-main@aarch64 as a component of Red Hat Hardened Images; jq-main@src as a component of Red Hat Hardened Images; jq-main@x86_64 as a component of Red Hat Hardened Images
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.