Skip to main content
VulnerabilityPublished Updated

CVE-2025-27650: Vasion Print · Insufficiently Protected Credentials

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 22.0.862 : patch affected systems as a priority.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 22.0.862
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

AI-suggested

1. 2. Until patches are deployed, isolate Docker overlay networks used by Vasion Print from untrusted networks to limit exposure. 3. Rotate all private keys associated with the affected components to invalidate potentially compromised credentials. 4. Implement strict network segmentation and access controls around containerized print management environments. 5. Monitor network traffic and system logs for unusual access patterns or attempts to extract sensitive keys. 6. Employ container security best practices, including scanning images for vulnerabilities and restricting container privileges. 7. Engage with Vasion Print support and subscribe to security advisories for timely updates. 8. Conduct security audits focusing on cryptographic key management and Docker overlay configurations. 9. Educate IT staff on the risks of insecure key storage and the importance of secure container orchestration. 10. Consider deploying runtime security tools that can detect anomalous container behavior indicative of exploitation attempts.

Description

Vasion Print (formerly PrinterLogic) before Virtual Appliance Host 22.0.862 Application 20.0.2014 allows Private Keys in Docker Overlay V-2023-013.

References

Community reviews

Loading reviews…