Skip to main content
VulnerabilityPublished

CVE-2026-127106: CWE-779

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-127106· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 20 Nov 2026, 19:47 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.15.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Exploit Intelligenceexploit-intelligence/agent-client-rhel9Affected–Fixed in–
Red Hat build of Quarkusquarkus-rest-jsonbAffected–Fixed in–

AI-suggested

Currently, no mitigation or patch meeting Red Hat's criteria for ease of use, applicability, or stability is available. Deployments not using JSON-B with flexible or recursive types (e.g., using Jackson or strict schemas) are not vulnerable. Monitor vendor advisories for future updates or fixes.

Description

A vulnerability in the quarkus-rest-jsonb component of Quarkus allows an unauthenticated remote attacker to cause a Denial of Service (DoS) by sending HTTP requests with deeply nested JSON payloads. This triggers excessive logging of large error traces, which can exhaust disk space or overwhelm log processing, degrading service availability. The impact is limited to availability degradation without affecting confidentiality or integrity. No patch or mitigation meeting Red Hat's criteria is currently available. The vulnerability affects deployments using JSON-B with flexible or recursive types, while those using other serialization frameworks or strict schemas are not vulnerable.

References

Community reviews

Loading reviews…