CVE-2026-42100

Sparxsystems Pro Cloud Server vulnerability

7.5 HIGHPublic exploitEPSS 0.64%

Published19 May 2026

Description

Improper Handling of Syntactically Invalid Structure in Sparx Pro Cloud Server allows Denial of Service (DoS) attack to be executed by sending an specially crafted SQL query. This causes the Pro Cloud Server service to terminate unexpectedly. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.1 (build 167) and below were tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityNone

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Sparxsystems Pro Cloud Server≤ 6.1.167

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://cert.pl/en/posts/2026/05/CVE-2026-42096Third Party Advisory
https://efigo.pl/blog/CVE-2026-42096/Third Party Advisory
https://sparxsystems.com/products/procloudserver/Product
https://sploit.tech/2026/05/19/Sparx-Enterprise-Architect-PCS.htmlExploitThird Party Advisory

Frequently asked

Is CVE-2026-42100 being actively exploited?

CVE-2026-42100 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.64%.

How severe is CVE-2026-42100?

CVE-2026-42100 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.64% probability of exploitation.

Which products are affected by CVE-2026-42100?

Affected products include Sparxsystems Pro Cloud Server.

How do I fix CVE-2026-42100?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-42100 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.