CVE
CIPCarbone Farmasimplex server impersonation in healthcare integration modules
Farmasimplex versions before 16.2.0 are affected through improper TLS certificate checks in their integration modules. The fix is in 16.2.0.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:U
- Exploited
- No known exploitation
- Fix
- Fixed in 16.2.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 16.2.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- 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? →
- 25/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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Farmasimplex healthcare integration modules from CIPCarbone do not properly validate TLS certificates. A remote attacker who can intercept network traffic, without logging in, could impersonate trusted healthcare services and possibly read or change sensitive data.
Original description
Multiple Farmasimplex healthcare integration modules do not properly validate TLS certificates, allowing an attacker who can intercept network traffic to impersonate trusted healthcare services and perform man-in-the-middle attacks, potentially leading to disclosure or modification of sensitive data.
Who should check
Pharmacies and vendors running CIPCarbone Farmasimplex versions before 16.2.0 with healthcare integration modules.
“Farmasimplex, versioni precedenti alla 16.2.0”
cve.now Index
- Exploitation0/40No signal
- 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
- Severity8.1/10CVSS 7.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 16.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123050 (Improper TLS Certificate Validation in Farmasimplex Healthcare Integration Modules), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-123050 (entry last updated 2026-11-17):
Affected:
- CIPCarbone Farmasimplex: fixed in 16.2.0
Fixed versions: 16.2.0.
Conditions (all must be true for the bug to be hit):
- Farmasimplex versions prior to 16.2.0 are affected. (source: https://www.acn.gov.it/portale/w/rilevate-vulnerabilita-in-farmasimplex)
- The flaw is in the TLS certificate checks implemented in the integration modules. (source: https://www.acn.gov.it/portale/w/rilevate-vulnerabilita-in-farmasimplex)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-123050 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123050 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.acn.gov.it/portale/w/rilevate-vulnerabilita-in-farmasimplex
- https://www.cipcarbone.it/extra.php?indice=13
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-123050
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123050"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- CIPCarbone Farmasimplex
fixed in 16.2.0
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123050
Is CVE-2026-123050 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 integration modules do not properly check TLS certificates. An attacker who can intercept network traffic can impersonate legitimate services, carry out man-in-the-middle attacks, access sensitive information, or alter exchanged data.Source: acn.gov.it
Which versions are affected by CVE-2026-123050?
Farmasimplex: before 16.2.0.Source: cve.now feed data
Am I affected, and how do I check?
Farmasimplex versions prior to 16.2.0 are affected, specifically the TLS certificate checks in its integration modules. To check an installed copy, compare its version against 16.2.0.Source: acn.gov.it
How do I fix CVE-2026-123050?
Upgrade Farmasimplex to version 16.2.0 or later, which is the listed fixed version.Source: acn.gov.it