Skip to main content
CVE-2025-67397VulnerabilityPublished Updated

CVE-2025-67397: Passy · n/a

Affects PassySource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  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

Affected software

ProductAffectedFixed in
GitHubgiulioschiavone/Passypkg:github/giulioschiavone/PassyOther threatsAffected
  • =1.6.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Restrict access to Passy management interfaces strictly to trusted, authenticated users with the minimum necessary privileges. 2. Implement network segmentation and firewall rules to limit exposure of Passy HTTP endpoints to internal or highly controlled networks. 3. Monitor HTTP traffic for anomalous or suspicious payloads indicative of command injection attempts, using IDS/IPS or web application firewalls with custom rules tailored to detect command injection patterns. 4. Conduct thorough audits of user accounts and privilege assignments to ensure no excessive privileges are granted unnecessarily. 5. Prepare for rapid deployment of patches or updates once available by establishing a vulnerability management process specific to Passy. 6. Employ application-layer input validation and sanitization where possible to reduce injection risks. 7. Use multi-factor authentication to reduce the risk of credential compromise leading to authenticated access. 8. Maintain comprehensive logging and alerting to detect and respond to suspicious activities promptly. 9. Engage with Passy vendor or community to obtain updates and security advisories. 10. Consider temporary compensating controls such as disabling vulnerable features or services if feasible until patches are released.

Description

An issue in Passy v.1.6.3 allows a remote authenticated attacker to execute arbitrary commands via a crafted HTTP request using a specific payload injection.

References

Community reviews

Loading reviews…