How severe is CVE-2018-19276?

CVE-2018-19276 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-19276?

Affected package information for CVE-2018-19276 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-19276?

No fixed version has been published for CVE-2018-19276 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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

Yes. There are 10 known exploit references for CVE-2018-19276, including 2 documented proof-of-concept exploits on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2018-19276 has an EPSS (Exploit Prediction Scoring System) score of 93.3%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-19276?

CVE-2018-19276 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2018-19276?

A Nuclei detection template exists for CVE-2018-19276, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2018-19276 was published on March 21, 2019 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2018-19276

CRITICAL

Published

Mar 21, 2019

Updated

Mar 14, 2026

Affected

0 pkgs

Patched

None yet

Exploits

10 known

EPSS Exploitation Probability

via FIRST.org ↗

93.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

OpenMRS before 2.24.0 is affected by an Insecure Object Deserialization vulnerability that allows an unauthenticated user to execute arbitrary commands on the targeted system via crafted XML data in a request body.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46327webappsjava

OpenMRS Platform < 2.24.0 - Insecure Object Deserialization

by Bishop Fox · Feb 5, 2019

Exploit-DB Source

EDB-47792remotelinux✓ Verified

OpenMRS - Java Deserialization RCE (Metasploit)

by Metasploit · Dec 18, 2019

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-19276 in your stack?

O3 detects CVE-2018-19276 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works