ManageIQ / ManageIQ/foreman_api_client
CVE-2026-33210 (High) detected in json-2.15.0.gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
## CVE-2026-33210 - High Severity Vulnerability
Vulnerable Library - json-2.15.0.gem
This is a JSON implementation as a Ruby extension in C.
Library home page: https://rubygems.org/gems/json-2.15.0.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/json-2.15.0.gem
Dependency Hierarchy:
- manageiq-style-1.5.8.gem (Root Library)
- rubocop-performance-1.23.1.gem
- rubocop-1.56.3.gem
- :x: **json-2.15.0.gem** (Vulnerable Library)
Found in base branch: master
Ruby JSON is a JSON implementation for Ruby. From version 2.14.0 to before versions 2.15.2.1, 2.17.1.2, and 2.19.2, a format string injection vulnerability can lead to denial of service attacks or information disclosure, when the allow_duplicate_key: false parsing option is used to parse user supplied documents. This issue has been patched in versions 2.15.2.1, 2.17.1.2, and 2.19.2.
Publish Date: 2026-03-20
URL: CVE-2026-33210
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-3m6g-2423-7cp3
Release Date: 2026-03-19
Fix Resolution: json - 2.19.2,json - 2.17.1.2,json - 2.15.2.1
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting Gemfile.lock and vendor/cache/json-2.15.0.gem, then trace the rubocop-performance dependency path described in the issue. Update the resolved json dependency to one of the listed fixed versions and verify that the vulnerable version is gone from both dependency records; run the available project checks afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100