How severe is CVE-2018-10054?

CVE-2018-10054 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-10054?

CVE-2018-10054 affects the following packages: com.datomic:datomic-free (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-10054?

Update com.datomic:datomic-free to 0.9.5697 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10054 is resolved across your whole dependency graph.

How do I detect CVE-2018-10054 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datomic:datomic-free, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-10054 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-10054 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-10054 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-10054?

CVE-2018-10054 has an EPSS (Exploit Prediction Scoring System) score of 33.7%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2018-10054?

CVE-2018-10054 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-10054 published, and has it been updated?

CVE-2018-10054 was published on April 11, 2018 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2018-10054 — datomic-free

HIGH

CVE-2018-10054 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in com.datomic:datomic-free. EPSS puts its 30-day exploitation probability at 33.7% (98th percentile). A fix is available for com.datomic:datomic-free — see the affected versions and patch details below.

Improper Input Validation in Datomic

Also known asGHSA-9pf8-qqhm-7w64

Published

Apr 11, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2018-10054.

EPSS Exploitation Probability

via FIRST.org ↗

33.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.datomic:datomic-free

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

H2 1.4.197, as used in Datomic before 0.9.5697 and other products, allows remote code execution because CREATE ALIAS can execute arbitrary Java code. NOTE: the vendor's position is "h2 is not designed to be run outside of a secure environment."

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.datomic:datomic-free`	all versions	0.9.5697`com.datomic:datomic-free:0.9.5697`

Affected Products

2 products · 2 configurations

Application

datomiccognitect

< 0.9.5697

range

Application

h2h2database

1 version

1.4.197

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datomic:datomic-free, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.datomic:datomic-free to 0.9.5697 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10054 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-10054 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works