CVE-2023-39913

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.5% (73rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Deserialization of Untrusted Data, Improper Input Validation vulnerability in Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK.This issue affects Apache UIMA Java SDK: before 3.5.0.

Users are recommended to upgrade to version 3.5.0, which fixes the issue.

There are several locations in the code where serialized Java objects are deserialized without verifying the data. This affects in particular: * the deserialization of a Java-serialized CAS, but also other binary CAS formats that include TSI information using the CasIOUtils class; * the CAS Editor Eclipse plugin which uses the the CasIOUtils class to load data; * the deserialization of a Java-serialized CAS of the Vinci Analysis Engine service which can receive using Java-serialized CAS objects over network connections; * the CasAnnotationViewerApplet and the CasTreeViewerApplet; * the checkpointing feature of the CPE module.

Note that the UIMA framework by default does not start any remotely accessible services (i.e. Vinci) that would be vulnerable to this issue. A user or developer would need to make an active choice to start such a service. However, users or developers may use the CasIOUtils in their own applications and services to parse serialized CAS data. They are affected by this issue unless they ensure that the data passed to CasIOUtils is not a serialized Java object.

When using Vinci or using CasIOUtils in own services/applications, the unrestricted deserialization of Java-serialized CAS files may allow arbitrary (remote) code execution.

As a remedy, it is possible to set up a global or context-specific ObjectInputFilter (cf. https://openjdk.org/jeps/290  and  https://openjdk.org/jeps/415 ) if running UIMA on a Java version that supports it.

Note that Java 1.8 does not support the ObjectInputFilter, so there is no remedy when running on this out-of-support platform. An upgrade to a recent Java version is strongly recommended if you need to secure an UIMA version that is affected by this issue.

To mitigate the issue on a Java 9+ platform, you can configure a filter pattern through the "jdk.serialFilter" system property using a semicolon as a separator:

To allow deserializing Java-serialized binary CASes, add the classes: * org.apache.uima.cas.impl.CASCompleteSerializer * org.apache.uima.cas.impl.CASMgrSerializer * org.apache.uima.cas.impl.CASSerializer * java.lang.String

To allow deserializing CPE Checkpoint data, add the following classes (and any custom classes your application uses to store its checkpoints): * org.apache.uima.collection.impl.cpm.CheckpointData * org.apache.uima.util.ProcessTrace * org.apache.uima.util.impl.ProcessTrace_impl * org.apache.uima.collection.base_cpm.SynchPoint

Make sure to use "!*" as the final component to the filter pattern to disallow deserialization of any classes not listed in the pattern.

Apache UIMA 3.5.0 uses tightly scoped ObjectInputFilters when reading Java-serialized data depending on the type of data being expected. Configuring a global filter is not necessary with this version.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.5%
EPSS %ILE
73rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 8, 2023

Last Modified

February 13, 2025

Advisory Details (2)

Auto-updated Aug 21, 2026
Patch available.
Web page
https://lists.apache.org/thread/lw30f4qlq3mhkhpljj16qw4fot3rg7v4
Web page

oss-security - CVE-2023-39913: Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK: Potential untrusted code execution when deserializing certain binary CAS formats

http://www.openwall.com/lists/oss-security/2023/11/08/1

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.uima:uimaj2.3.1
  • every version up to 3.5.0: fixed in 3.5.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 85 of 201 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 100 are merged into the row they repeat. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  4. 2026-10-20 23:29 UTCEG score recompute
  5. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  6. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  7. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  8. 2026-10-18 07:54 UTCEG score recompute
  9. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  11. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  14. 2026-10-12 18:21 UTCEG score recompute
  15. 2026-10-12 17:24 UTCOSV refresh
  16. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  17. 2026-10-11 21:47 UTCEG score recompute
  18. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  20. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  21. 2026-10-08 17:06 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  23. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  24. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
Show 60 more
  1. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  2. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-09-30 16:28 UTCEG score recompute
  4. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  5. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  6. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  7. 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  8. 2026-09-26 15:56 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  9. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  10. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  11. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  12. 2026-09-22 16:58 UTCOSV refresh
  13. 2026-09-18 19:25 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  14. 2026-09-17 19:25 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  15. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  16. 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  17. 2026-09-13 16:44 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  18. 2026-09-12 14:58 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  19. 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  20. 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  21. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  22. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  23. 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  24. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  25. 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  26. 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  27. 2026-09-03 13:29 UTCOSV refresh
  28. 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  29. 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  30. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  31. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  32. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  33. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  34. 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  35. 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  36. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  37. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  38. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  39. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  40. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  41. 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  42. 2026-08-17 03:18 UTCOSV refresh
  43. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  44. 2026-08-16 02:12 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  45. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  46. 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  47. 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  48. 2026-08-11 13:39 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  49. 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  50. 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  51. 2026-08-07 16:25 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  52. 2026-08-06 13:45 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  53. 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  54. 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  55. 2026-08-03 10:34 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  56. 2026-08-02 02:25 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  57. 2026-08-01 21:36 UTCOSV refresh
  58. 2026-08-01 04:13 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  59. 2026-07-30 16:26 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  60. 2026-07-30 01:28 UTCEPSS rescoreEPSS 1.5% · 71st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-39913?
CVE-2023-39913 is a high-severity vulnerability; its CVE record was published on November 8, 2023. Deserialization of Untrusted Data, Improper Input Validation vulnerability in Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK.This issue affects Apache UIMA Java SDK: before 3.5.0. Users are recommended to upgrade to version 3.5.0, which fixes the issue. There…
When was the CVE record for CVE-2023-39913 published?
The CVE record for CVE-2023-39913 was published on November 8, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of February 13, 2025; the record at its source may have been updated since.
Is CVE-2023-39913 actively exploited?
CVE-2023-39913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-39913?
CVE-2023-39913 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2023-39913?
A fix for CVE-2023-39913 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-39913

Explore →

Is Your Infrastructure Affected by CVE-2023-39913?

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

Book a Demo →Browse All CVEs