CVE-2022-32965

CRITICALNVD 9.89.8—

9.8

OMICARD EDM has a hard-coded machine key. An unauthenticated remote attacker can use the machine key to send serialized payload to the server to execute arbitrary code, manipulate system data and disrupt service.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 85.8%
KEV: Not listed

Published

August 4, 2022

Last Modified

November 21, 2024

References (4)

twcert@certhttps://www.chtsecurity.com/news/48032532-b2de-401c-97a8-a2be5691988f
twcert@certhttps://www.twcert.org.tw/tw/cp-132-6373-34d51-1.html
af854a3a-2127-422b-91ae-364da2661108https://www.chtsecurity.com/news/48032532-b2de-401c-97a8-a2be5691988f
af854a3a-2127-422b-91ae-364da2661108https://www.twcert.org.tw/tw/cp-132-6373-34d51-1.html

Weakness Classification(1)

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

CWE-798Use of Hard-coded Credentials

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2022-32965?

CVE-2022-32965 is a critical vulnerability published on August 4, 2022. OMICARD EDM has a hard-coded machine key. An unauthenticated remote attacker can use the machine key to send serialized payload to the server to execute arbitrary code, manipulate system data and disrupt service.

When was CVE-2022-32965 disclosed?

CVE-2022-32965 was first published in the National Vulnerability Database on August 4, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-32965 actively exploited?

CVE-2022-32965 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-32965?

CVE-2022-32965 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2022-32965?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-32965, 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-2022-32965

Explore →

Is Your Infrastructure Affected by CVE-2022-32965?

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

Start Free Scan →Browse All CVEs

CVE-2022-32965

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-32965?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)