Skip to main content
VulnerabilityPublished

CVE-2026-123051: CIPCarbone srl Farmasimplex REV.exe · Use of Hard-coded Credentials

Affects CIPCarbone srl Farmasimplex REV.exeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.2 Low : upgrade to 16.2.0 when convenient.

Data as of 17 Nov 2026, 14:54 UTC

CVSS 4.0 base score
1.2Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (ENISA)CVSS 4.01.2
Patch
Available – fixed in 16.2.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade CIPCarbone srl Farmasimplex REV.exe to 16.2.0.

Affected software

ProductAffectedFixed in
CIPCarbone srlFarmasimplex REV.exeAffected
  • <16.2.0
Fixed in
  • 16.2.0

AI-suggested

Upgrade Farmasimplex REV.exe to version 16.2.0 or later, where the hard-coded credential issue has been fixed. No additional mitigation is required if the system is updated to this fixed version.

Description

CVE-2026-123051 is a low-severity vulnerability in the Farmasimplex REV.exe module by CIPCarbone srl. The executable contains hard-coded OAuth client credentials used for integration with the IZS platform. An attacker who obtains the executable could extract these credentials and potentially misuse them to access integration resources or manipulate data, depending on the privileges and authentication controls. This issue is fixed in version 16.2.0.

References

Community reviews

Loading reviews…