Actively exploited

CVE-2019-0344 SAP Commerce Cloud Deserialization of Untrusted Data Vulnerability

SAP Commerce Cloud (formerly known as Hybris) contains a deserialization of untrusted data vulnerability within the mediaconversion and virtualjdbc extension that allows for code injection.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment

CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 30 Sep 2024.
Rated Critical severity (CVSS 9.8, scored by CISA).
It has been in the catalogue for 767 days. Systems still unpatched now have almost certainly been scanned for it.

The Vulnerability

What It Is

Due to unsafe deserialization used in SAP Commerce Cloud (virtualjdbc extension), versions 6.4, 6.5, 6.6, 6.7, 1808, 1811, 1905, it is possible to execute arbitrary code on a target machine with 'Hybris' user rights, resulting in Code Injection.

Affected Versions

Product	Versions
SAP SE SAP Commerce Cloud (virtualjdbc extension)	< 6.4 < 6.5 < 6.6 < 6.7 < 1808 < 1811

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

1
Find it
Search your asset inventory and external attack surface for SAP Commerce Cloud. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management
2
Fix it
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vulnerability Management
3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response
4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated critical, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 21 Oct 2024 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited SAP Flaws

All 14 exploited SAP vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2019-0344 and every other exploited flaw on the list.

Check My Exposure

Evidence

PREVENTION

DETECTION & MITIGATION

GRC

INCIDENT RESPONSE

CLOUD SECURITY

CRITICAL INFRASTRUCTURE

REGULATED SERVICES

PUBLIC SERVICES

COMMERCIAL

THREAT INTELLIGENCE

MANAGED SECURITY

NETWORK & CLOUD

RISK & COMPLIANCE

DATA & APPLICATIONS

PEOPLE & EMAIL

FOR VENDORS

CVE-2019-0344 SAP Commerce Cloud Deserialization of Untrusted Data Vulnerability

Should You Worry?

What It Is

Affected Versions

What To Do Now

Find it

Fix it

Hunt for compromise

Prove it is fixed

Vendor Advisories

The Compliance Clock

More Exploited SAP Flaws

Not Sure If You Are Exposed?

Sources