CVE-2026-50193

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 27, 2026

Advisory Details (3)

Auto-updated Jun 24, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Deeply 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-2prh
generic

Deeply nested JsonNode throws StackOverflowError for toString() [CVE-2026-50193] · Issue #3447 · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/issues/3447
github_commit

commit a1fa4ae4ecf5 (FasterXML/jackson-databind)

Fix landed in FasterXML/jackson-databind commit a1fa4ae4ecf5 — awaiting tagged release

https://github.com/FasterXML/jackson-databind/commit/a1fa4ae4ecf5cee16da465985f135f3e81816f8c

Patch Availability(22)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.12.1-1 ... 2.14.0-1 (10 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0-1
Maven(1)
PackageVulnerable rangeFixed inDependents
com.fasterxml.jackson.core:jackson-databind2.10.0 ... 2.14.0-rc3 (44 versions)2.14.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 10:23 UTCEG score recompute
  3. 2026-09-18 10:23 UTCVendor advisory
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-14 02:05 UTCEG score recompute
  7. 2026-09-14 02:05 UTCVendor advisory
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-13 12:21 UTCEG score recompute
  10. 2026-09-13 12:21 UTCVendor advisory
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-10 09:35 UTCEPSS rescore
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-09-01 04:40 UTCEPSS rescore
  20. 2026-08-30 20:25 UTCEG score recompute
  21. 2026-08-30 20:25 UTCVendor advisory
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 22:05 UTCEG score recompute
  4. 2026-08-24 22:05 UTCVendor advisory
  5. 2026-08-24 05:03 UTCVendor advisory
  6. 2026-08-23 15:58 UTCVendor advisory
  7. 2026-08-23 02:53 UTCEG score recompute
  8. 2026-08-23 02:53 UTCVendor advisory
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 13:44 UTCEG score recompute
  11. 2026-08-22 13:44 UTCVendor advisory
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 23:20 UTCVendor advisory
  14. 2026-08-21 09:55 UTCEG score recompute
  15. 2026-08-21 09:55 UTCVendor advisory
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 20:50 UTCVendor advisory
  18. 2026-08-20 07:45 UTCEG score recompute
  19. 2026-08-20 07:45 UTCVendor advisory
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 04:48 UTCEG score recompute
  22. 2026-08-19 04:48 UTCVendor advisory
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 09:15 UTCVendor advisory
  26. 2026-08-16 20:11 UTCEG score recompute
  27. 2026-08-16 20:11 UTCVendor advisory
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 06:21 UTCEG score recompute
  30. 2026-08-16 06:21 UTCVendor advisory
  31. 2026-08-16 02:14 UTCEPSS rescore
  32. 2026-08-15 17:17 UTCVendor advisory
  33. 2026-08-15 04:12 UTCEG score recompute
  34. 2026-08-15 04:12 UTCVendor advisory
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 15:06 UTCVendor advisory
  37. 2026-08-14 02:01 UTCEG score recompute
  38. 2026-08-14 02:01 UTCVendor advisory
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-13 12:56 UTCVendor advisory
  41. 2026-08-12 23:52 UTCEG score recompute
  42. 2026-08-12 23:52 UTCVendor advisory
  43. 2026-08-12 13:51 UTCEPSS rescore
  44. 2026-08-12 10:47 UTCVendor advisory
  45. 2026-08-11 21:42 UTCEG score recompute
  46. 2026-08-11 21:42 UTCVendor advisory
  47. 2026-08-11 08:37 UTCEG score recompute
  48. 2026-08-11 08:37 UTCVendor advisory
  49. 2026-08-11 00:00 UTCEPSS rescore
  50. 2026-08-10 19:32 UTCVendor advisory
  51. 2026-08-10 06:26 UTCVendor advisory
  52. 2026-08-09 17:21 UTCEG score recompute
  53. 2026-08-09 17:21 UTCVendor advisory
  54. 2026-08-09 13:46 UTCEPSS rescore
  55. 2026-08-09 04:17 UTCEG score recompute
  56. 2026-08-09 04:17 UTCVendor advisory
  57. 2026-08-08 16:37 UTCEPSS rescore
  58. 2026-08-08 15:12 UTCVendor advisory
  59. 2026-08-08 02:07 UTCEG score recompute
  60. 2026-08-08 02:07 UTCVendor advisory
  61. 2026-08-07 13:02 UTCVendor advisory
  62. 2026-08-06 23:57 UTCEG score recompute
  63. 2026-08-06 23:57 UTCVendor advisory
  64. 2026-08-06 13:47 UTCEPSS rescore
  65. 2026-08-06 10:53 UTCVendor advisory
  66. 2026-08-05 21:47 UTCEG score recompute
  67. 2026-08-05 21:47 UTCVendor advisory
  68. 2026-08-05 19:17 UTCEPSS rescore
  69. 2026-08-05 08:42 UTCVendor advisory
  70. 2026-08-04 16:25 UTCEG score recompute
  71. 2026-08-04 16:25 UTCVendor advisory
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 10:39 UTCEPSS rescore
  74. 2026-08-04 03:20 UTCVendor advisory
  75. 2026-08-03 14:15 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50193?
CVE-2026-50193 is a high vulnerability published on June 23, 2026. 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…
When was CVE-2026-50193 disclosed?
CVE-2026-50193 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50193 actively exploited?
CVE-2026-50193 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.9% of all scored CVEs.
What is the CVSS score of CVE-2026-50193?
CVE-2026-50193 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50193?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50193, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50193

Explore →

Is Your Infrastructure Affected by CVE-2026-50193?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.