ApplicationsHigh 8.5Patch available
CVE-2026-129784
HTTPX gem RCE via Oj unsafe JSON deserialization
How scary is it?
updated 20 Nov 2026- No
Works without logging in1
Needs a login: a basic user account (CVSS PR:L).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild
None reported that we know of.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run os85 httpx in an affected version>= 1.9.0 and < 1.9.1
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
The attacker has a user account
CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.
Source 1
Specific conditions are met that the attacker does not control
CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade httpx to >=1.9.1; avoid Oj :object mode or validate/whitelist fetched URLs
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
- CVSS
- 8.5Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.66%chance of exploitation in the next 30 daystop 48% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 16 Nov 2026analysed here 16 Nov 2026
Summary
Impact
Remote code execution by attacker-controlled URL causing Oj to instantiate arbitrary Ruby objects during JSON parsing.
Triage
Executive summary (AI-written)
A significant vulnerability identified as CVE-2026-129784 has been discovered in the HTTPX gem, which is widely used in Ruby applications. With a CVSS score of 8.5, this vulnerability poses a standard severity level and can potentially lead to remote code execution (RCE) by exploiting unsafe JSON deserialization through the Oj library. This means that an attacker could execute arbitrary Ruby code on affected systems, leading to serious security breaches and operational disruptions. Given its implications, organizations utilizing HTTPX in their Ruby applications are strongly advised to take immediate action to mitigate any associated risks.
Technical analysis (AI-written)
CVE-2026-129784 involves a remote code execution vulnerability in the HTTPX gem due to its integration with the Oj library handling JSON parsing. When the Oj gem processes inputs in its default :object mode, it allows an attacker to control URL inputs, resulting in the instantiation of arbitrary Ruby objects. This poses a significant risk, as it enables attackers to exploit vulnerable applications to execute malicious Ruby code. The affected versions are identified as httpx 1.9.0, and applications that utilize oj without multi_json are particularly vulnerable. The attack vector involves sending specially crafted JSON content containing malicious URLs to the application that utilizes the affected HTTPX gem. If the application processes this JSON using Oj in a vulnerable configuration, it can trigger the execution of arbitrary code, thereby compromising the application and potentially the underlying system. The complexity of exploitation is moderate; an attacker would need to have the capability to send requests to the application and manipulate the JSON data appropriately. To mitigate this vulnerability, it is crucial to upgrade the HTTPX gem to version 1.9.1 or later, where this issue has been addressed. In addition to upgrading, developers should avoid using Oj in :object mode for untrusted data deserialization. Furthermore, implementing URL validation and whitelisting for retrieved URLs can help prevent attackers from exploiting this vulnerability effectively. Conducting a thorough audit of applications using the HTTPX gem would also ensure that any potential exposure to this vulnerability is identified and remediated without delay. As this threat specifically targets Ruby applications using the HTTPX gem alongside Oj, organizations must prioritize this patching process. Ignoring this vulnerability opens the door for severe security incidents that could compromise data integrity and overall system security. Therefore, immediate action is required to protect against this high-severity threat, especially in sectors reliant on Ruby-based application deployments.
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| os85 httpx | >= 1.9.0 and < 1.9.1Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- httpx 1.9.0
- Ruby applications using httpx with oj loaded and multi_json absent
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.
Also consider: allow-list classes · patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
Timeline
- 16 Nov 2026Published
- 16 Nov 2026CVE record last updatedsame day later
- 16 Nov 2026Analysed by vulneraibility.comsame day later
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | HighNeeds specific conditions, a race or a particular configuration. | Needs specific conditions, a race or a particular configuration. |
| Privileges required | LowThe attacker needs basic user privileges. | The attacker needs basic user privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | ChangedImpact crosses a security boundary into other components. | Impact crosses a security boundary into other components. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2026-129784 being exploited?
Not confirmed. CVE-2026-129784 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.66% probability of exploitation in the next 30 days.
How severe is CVE-2026-129784?
CVE-2026-129784 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-129784?
Yes. A fix has been recorded for CVE-2026-129784. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-129784 affect?
CVE-2026-129784 affects httpx 1.9.0, Ruby applications using httpx with oj loaded and multi_json absent. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-129784?
Upgrade httpx to >=1.9.1; avoid Oj :object mode or validate/whitelist fetched URLs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
7 references in the CVE record, grouped by the tags the record gives them.
Patches (3)
- github.com /HoneyryderChuck/httpx/commit/eeb785d3250eee9379494fb62c37c315a31e327c
- github.com /HoneyryderChuck/httpx/releases/tag/v1.9.1
- gitlab.com /os85/httpx/-/commit/eeb785d3250eee9379494fb62c37c315a31e327c
Other links (4)
- github.com /HoneyryderChuck/httpx
- rubygems.org /gems/httpx
- github.com /ohler55/oj/blob/develop/pages/Security.md
- gitlab.com /os85/httpx
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.