jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.13.0 until 2.14.0, a potential Denial-of-Service exists when attacker sends deeply nested JSON if (and only if) the service reads deeply nested (1000s of levels) JSON as JsonNode (ObjectMapper.readTree()) and writes out same (or modifided) node using JsonNode.toString(). This can consume significant amount of resources with concurrent relatively small requests (1000 nested arrays is 2kB). This vulnerability is fixed in 2.14.0.
CVE-2026-50193
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 45.2%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
June 27, 2026
Advisory Details (3)
Auto-updated Jun 24, 2026Deeply nested JsonNode throws StackOverflowError for toString() · Advisory · FasterXML/jackson-databind · GitHub
Affected: 2.14.0 via
https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-3wrr-7qpf-2prhDeeply nested JsonNode throws StackOverflowError for toString() [CVE-2026-50193] · Issue #3447 · FasterXML/jackson-databind · GitHub
https://github.com/FasterXML/jackson-databind/issues/3447commit a1fa4ae4ecf5 (FasterXML/jackson-databind)
Fix landed in FasterXML/jackson-databind commit a1fa4ae4ecf5 — awaiting tagged release
https://github.com/FasterXML/jackson-databind/commit/a1fa4ae4ecf5cee16da465985f135f3e81816f8cVendor Advisories for CVE-2026-50193(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 37× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 22:41 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 09:36 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 20:30 UTCEG score recompute
- 2026-07-05 07:24 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 18:18 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 05:02 UTCEG score recompute
- 2026-07-03 15:55 UTCEG score recompute
- 2026-07-03 02:49 UTCEG score recompute
- 2026-07-02 13:43 UTCEG score recompute
- 2026-07-02 00:38 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 11:33 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 22:28 UTCEG score recompute
- 2026-06-30 09:23 UTCEG score recompute
- 2026-06-29 20:18 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 07:14 UTCEG score recompute
- 2026-06-28 18:08 UTCEG score recompute▲ 1.20
- 2026-06-28 14:07 UTCEPSS rescore
Show 12 moreShow fewer
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 21:42 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-06-27 18:38 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:08 UTCEG score recompute
- 2026-06-25 19:39 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 20:09 UTCEG score recompute▲ 6.30
- 2026-06-24 20:03 UTCNVD updateCVSS v3 → 6.3 · CVSS v4 → 6.3
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:31 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-50193?
When was CVE-2026-50193 disclosed?
Is CVE-2026-50193 actively exploited?
What is the CVSS score of CVE-2026-50193?
How do I remediate CVE-2026-50193?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-50193
Is Your Infrastructure Affected by CVE-2026-50193?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.