Skip to content
Fencer Intel
medium 5.3

CVE-2026-127106 json

Quarkus-rest-jsonb: deeply nested json-b bodies cause large stack-trace logs in quarkus rest

published 8h ago modified 7h ago also EUVD-2026-131701

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

A flaw was found in the quarkus-rest-jsonb component of Quarkus. An unauthenticated remote attacker can cause a Denial of Service (DoS) by sending HTTP requests containing deeply nested JSON payloads to vulnerable endpoints. The application fails during JSON parsing and records an excessively large error trace for each small request. This disproportionate log amplification can exhaust system disk space or overwhelm log processing pipelines, degrading service availability.

Is CVE-2026-127106 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-127106 updated cvss 5.3

quarkus-rest-jsonb: Deeply nested JSON-B bodies cause large stack-trace logs in Quarkus REST

  • Red Hat Exploit Intelligence exploit-intelligence/agent-client-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Quarkus quarkus-rest-jsonb
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected products

  • Red Hat Exploit Intelligence
  • Red Hat Red Hat build of Quarkus

Classification

Weakness
  • CWE-779 Logging of Excessive Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.