Secuno
ENNL
Book demo

CVE-2025-67221

Ijl Orjson denial of service

7.5 HIGHPublic exploitEPSS 0.64%
  1. Published22 Jan 2026

Description

The orjson.dumps function in orjson thru 3.11.4 does not limit recursion for deeply nested JSON documents.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Ijl Orjson≤ 3.11.4

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1031028.6
Pexip Infinity before 41.0 is affected by improper input validation in the signaling…
CVE-2026-1031018.6
Pexip Infinity 30.0 through 40.x before 41.0 is affected by improper input validation…
CVE-2026-824399.8
Description The DRPC server kept a map from function name to request queue and created…
CVE-2026-478919.8
A Spring WebFlux application that relies on the Aalto XML processor to parse XML input…
CVE-2026-735418.2
Allocation of Resources Without Limits or Throttling in ZenHive mpp allows an…
CVE-2026-748789.8
openssl_encrypt versions before 1.4.0 use an in-memory rate limiter for TOTP…

Frequently asked

Is CVE-2025-67221 being actively exploited?

CVE-2025-67221 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.64%.

How severe is CVE-2025-67221?

CVE-2025-67221 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.64% probability of exploitation.

Which products are affected by CVE-2025-67221?

Affected products include Ijl Orjson.

How do I fix CVE-2025-67221?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-67221 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.