CVE
httpx possible code execution via Oj object-mode parsing
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 1.9.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The oj gem is loaded (and loaded before httpx) and multi_json is absent from the bundle. The process has not pinned a safe Oj.default_options. An attacker-influenced URL is passed to response.json. Code execution additionally requires a gadget chain in the process.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The httpx Ruby gem can let an attacker create instances of any already-loaded Ruby class in the application process when it parses a JSON response with the oj gem loaded. An attacker with low privileges who controls or influences a URL the application fetches over the network could potentially achieve remote code execution, depending on available gadget chains.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
The httpx Ruby gem parses JSON response bodies through its transcoder layer. HTTPX::Response#json delegates to Transcoder::JSON.decode, and when the oj gem is loaded and multi_json is absent, the decoder falls back to json_load, which calls Oj.load(response.to_s) with no mode option. Oj.load defaults to :object mode, in which a response document can allocate any already-loaded Ruby class ("^o":"ClassName") and set its instance variables, or resolve a class or module reference ("^c":"Name"). An attacker who controls, or can influence, the URL an application fetches with HTTPX.get(url).json therefore controls object instantiation in the victim process. With a matching gadget chain, this issue can potentially cause remote code execution. Affects httpx 1.9.0; fixed in 1.9.1.
Who should check
Teams running httpx 1.9.0 with oj loaded before httpx, without multi_json in the bundle, and calling response.json on URLs an attacker can influence.
“Affects httpx 1.9.0 only when the oj gem is loaded (and loaded before httpx)”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects RubyGems packages
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 35 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The oj gem is loaded (and loaded before httpx) and multi_json is absent from the bundle. The process has not pinned a safe Oj.default_options. An attacker-influenced URL is passed to response.json. Code execution additionally requires a gadget chain in the process.Upgrade to a fixed version: 1.9.1.
Workaround: Pass a safe mode at the call site (response.json(mode: :strict)), or set a safe process-wide default such as Oj.default_options = { mode: :strict } before untrusted JSON is parsed.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129784 (Insecure deserializaiton in the httpx Ruby gem via unsafe Oj object-mode), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129784 (entry last updated 2026-11-16):
Affected:
- RubyGems package httpx: from 1.9.0, fixed in 1.9.1
Fixed versions: 1.9.1.
Conditions (all must be true for the bug to be hit):
- The oj gem is loaded (and loaded before httpx) and multi_json is absent from the bundle. (source: https://www.cve.org/CVERecord?id=CVE-2026-129784)
- The process has not pinned a safe Oj.default_options. (source: https://www.cve.org/CVERecord?id=CVE-2026-129784)
- An attacker-influenced URL is passed to response.json. (source: https://www.cve.org/CVERecord?id=CVE-2026-129784)
- Code execution additionally requires a gadget chain in the process. (source: https://www.cve.org/CVERecord?id=CVE-2026-129784)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Pass a safe mode at the call site (response.json(mode: :strict)), or set a safe process-wide default such as Oj.default_options = { mode: :strict } before untrusted JSON is parsed. (source: https://www.cve.org/CVERecord?id=CVE-2026-129784)
CISA KEV: CVE-2026-129784 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129784 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (RubyGems): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/HoneyryderChuck/httpx/commit/eeb785d3250eee9379494fb62c37c315a31e327c
- https://github.com/HoneyryderChuck/httpx/releases/tag/v1.9.1
- https://gitlab.com/os85/httpx/-/commit/eeb785d3250eee9379494fb62c37c315a31e327c
- https://github.com/HoneyryderChuck/httpx
- https://rubygems.org/gems/httpx
- https://github.com/ohler55/oj/blob/develop/pages/Security.md
- https://gitlab.com/os85/httpx
- https://www.cve.org/CVERecord?id=CVE-2026-129784
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129784
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129784"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- httpxRubyGems
From 1.9.0 · fixed in 1.9.1
Fixed in 1.9.1 (released Nov 13, 2026, 3 days before disclosure).
The latest release, 1.9.1, is not affected.
Evidence 9
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 7
- Patch
- Patch
- Patch
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129784
Is CVE-2026-129784 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The httpx Ruby gem's response.json path can deserialize untrusted data through the Oj library in object mode, which can lead to insecure deserialization. Reaching code execution additionally requires a gadget chain in the process.Source: cve.org
Which versions are affected by CVE-2026-129784?
httpx (RubyGems): from 1.9.0 before 1.9.1.Source: cve.now feed data
Am I affected, and how do I check?
Affects httpx 1.9.0 only when the oj gem is loaded and loaded before httpx, and multi_json is absent from the bundle. It also requires that the process has not pinned a safe Oj.default_options and that an attacker-influenced URL is passed to response.json. Check the httpx version in your Gemfile.lock and whether the oj gem is in the bundle, and look for any Oj.default_options setting in your code.Source: cve.org
How do I fix CVE-2026-129784?
Upgrade to httpx 1.9.1, which calls Oj.load with an explicit { mode: :strict } default. If you cannot upgrade yet, pass mode: :strict at the call site or set Oj.default_options = { mode: :strict } before untrusted JSON is parsed.Source: cve.org