/

CVE-2026-86808

Severity:

HIGH RISK

(7.3)

Missing Authentication (CWE-306) in Moltis Vault Handlers

CVE-2026-86808

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-287, CWE-306

Impact:

Unauthorized Access to Vault Functionality

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing-authentication vulnerability in Moltis affects vault unlock and recovery handlers, allowing requests to reach sensitive functionality without the expected authentication checks.

Because the affected handlers can be reached remotely, an attacker may invoke vault operations without valid credentials when the vulnerable conditions are present.

Affected context

The issue occurs in Moltis deployments where the vault_unlock_handler or

vault_recovery_handler functions in vault.rs are exposed through a

remotely reachable interface without consistently enforcing authentication.

The exact exposure depends on deployment routing, handler configuration, and

whether other controls restrict access to these operations.

Exploit preconditions

  • Attack surface: Remotely reachable vault unlock or recovery endpoints
  • Required access: Network access to the affected handler; valid credentials may not be required
  • Trigger point: A request processed by vault_unlock_handler or vault_recovery_handler
  • Why exploitation is possible: The sensitive operation can be reached without a required authentication decision being enforced

Why this happens

The underlying bug is an authentication-control failure in which a security-sensitive

handler processes requests without first establishing that the caller is authorized.

This maps primarily to CWE-306: Missing Authentication for Critical Function.

It is also related to CWE-287: Improper Authentication when authentication logic

exists elsewhere but is incomplete, bypassable, or incorrectly applied to these paths.

Potential impact

  • An attacker may access protected vault functionality without valid credentials
  • Unauthorized users could potentially unlock, recover, or manipulate vault-related state
  • Confidential vault data may be exposed or altered
  • The compromise could enable further access to dependent application resources

General mitigation guidance

Mitigation generally focuses on making authentication mandatory and consistent for

every sensitive vault operation.

Common defensive patterns include:

  • Enforcing authentication at the handler boundary before any state-changing or sensitive action
  • Applying centralized authorization middleware rather than relying on individual callers
  • Denying access by default when authentication context is absent or invalid
  • Separating authentication from recovery logic and requiring independent authorization for recovery operations
  • Limiting service identities and permissions according to least privilege
  • Restricting network exposure of vault endpoints through authenticated gateways and policy controls
  • Avoiding reliance on obscurity, routing assumptions, or client-side checks as security controls

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis rules identifying sensitive handlers without authentication middleware or authorization checks
  • Code review checks confirming every vault unlock and recovery route has an explicit authentication boundary
  • Integration tests that verify unauthenticated, expired, and malformed authentication contexts are rejected
  • API gateway and service-mesh policies requiring identity verification for vault-related routes
  • Runtime monitoring for anonymous or unexpected principals invoking sensitive vault operations
  • Automated security review tools that flag critical functions reachable without access-control enforcement

Sources

SourceLink
github.comgithub.com/moltis-org/moltis/
github.comgithub.com/moltis-org/moltis/commit/3b92dd64d5648f829968cf48bf67dc3113852fef
github.comgithub.com/moltis-org/moltis/issues/1177
github.comgithub.com/moltis-org/moltis/pull/1216
github.comgithub.com/moltis-org/moltis/releases/tag/20260819.01
vuldb.comvuldb.com/cve/CVE-2026-86808
vuldb.comvuldb.com/submit/911081
vuldb.comvuldb.com/vuln/399813
vuldb.comvuldb.com/vuln/399813/cti

Frequently asked

questions

Yes. The affected vault handlers are described as remotely reachable, although practical exposure depends on network routing, deployment configuration, and surrounding access controls.

The vulnerability is characterized by missing authentication, so valid credentials may not be required when an attacker can reach an affected handler.

Require authentication and authorization at a centralized boundary before vault unlock or recovery logic executes, and deny requests when identity validation fails.

Protect sensitive routes with mandatory server-side access-control middleware, test unauthenticated and unauthorized cases in CI, and continuously monitor access to critical vault operations.

Find out what's already
exploitable in your codebase.