AIS XML parsers allow external entity resolution
CompuGroup Medical's Infantia, Profim, Phronesis and Venere are affected up to versions 6.01.1, 6.01.1, 4.51.0 and 8.33.2. CVSS rates it 7.2 (high). No fix is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround. The cause is an insecure configuration of the XML-parsing components, so reviewing and hardening how those components handle external resources is the relevant step until a fix is available.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AIS XML parsers that process attacker-influenced update manifests or network responses with external entity resolution enabled are potentially open to XML External Entity (XXE) attacks. An attacker can reach this remotely over the network, without logging in and without any user action.
Read the original description
XML parsers process attacker-influenced update manifests or network responses with external entity resolution enabled, potentially allowing XML External Entity (XXE) attacks.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts give no workaround. The cause is an insecure configuration of the XML-parsing components, so reviewing and hardening how those components handle external resources is the relevant step until a fix is available.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- CompuGroup Medical Infantia
through 6.01.1
- CompuGroup Medical Profim
through 6.01.1
- CompuGroup Medical Phronesis
through 4.51.0
- CompuGroup Medical Venere
through 8.33.2
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118468
Is CVE-2026-118468 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The XML parsing components in these products are configured insecurely, which allows access to external resources. The advisory says this can compromise the confidentiality, integrity and availability of the affected information and functions.Source: acn.gov.it
Which versions are affected by CVE-2026-118468?
Infantia: through 6.01.1. Profim: through 6.01.1. Phronesis: through 4.51.0. Venere: through 8.33.2.Source: cve.now feed data
Am I affected, and how do I check?
Infantia and Profim are affected up to and including 6.01.1, Phronesis up to and including 4.51.0, and Venere up to and including 8.33.2. To check an installation, compare the installed product version number against these limits.Source: acn.gov.it
How do I fix CVE-2026-118468?
The checked facts do not list a fixed version, so no upgrade target can be named. Check the vendor's advisory for an updated release of each affected product.Source: acn.gov.it
What if there's no patch?
The checked facts give no workaround. The cause is an insecure configuration of the XML-parsing components, so reviewing and hardening how those components handle external resources is the relevant step until a fix is available.Source: acn.gov.it