External risk intelligence

Secret Server Authentication Bypass Via Two-Factor PIN Generation.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-115829

Secret Server is a privileged access management (PAM) solution. These appliances or applications are designed to be internet-facing or reachable by remote administrators to manage credentials and secrets. Given the nature of the product, it is frequently exposed as a gateway for authentication and identity management.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Secret Server on-prem that allows an attacker to bypass authentication and gain access to accounts by exploiting a two-factor authentication flaw.

  • Bypass authentication for any account.
  • Protects sensitive privileged access.
  • Confirm relevance and exposure to sensitive data.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could exploit a flaw in Delinea Secret Server to bypass initial authentication steps and directly authenticate using only a two-factor PIN. This could lead to unauthorized access to sensitive information managed by the compromised account.

  • No prior authentication required.
  • Triggered by generating a two-factor PIN.
  • Risk of unauthorized account access.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a user could bypass authentication to generate a two-factor PIN for any account and then use that PIN to log in. This could potentially expose sensitive information managed by the Secret Server.

  • System data and user credentials at risk.
  • Bypass initial login, authenticate with second factor.
  • Unauthorized access to sensitive information.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in on-prem Secret Server impacts authentication mechanisms. The first step is to identify all instances, assess their reachability and business criticality, and then locate the accountable owners to plan a risk-based remediation.

  • Issue ownership by platform or security teams.
  • Verify external or internal reachability.
  • Plan remediation based on asset criticality.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Delinea Secret Server?

Secret Server is a privileged access management (PAM) solution used by organizations to securely store, manage, and rotate sensitive credentials, passwords, and secrets. It serves as a centralized vault, often acting as a critical gateway for administrators to access sensitive IT infrastructure, applications, and data.

What does CVE-2026-115829 mean?

This vulnerability, classified as CWE-288 (Authentication Bypass Using an Alternate Path or Channel), allows someone to circumvent the standard login process. By triggering the generation of a two-factor PIN without first providing a password, an attacker can use that PIN alone to gain unauthorized access to any account on an affected system.

How is this authentication bypass triggered?

An attacker can initiate the vulnerability by requesting a two-factor PIN for an account without needing to provide any primary credentials first. Simply interacting with the system's PIN generation feature in this way enables the flaw. Note that this requires access to the system's authentication interface, but it does not involve guessing passwords or requiring previous valid login sessions.

Is my Secret Server instance at risk?

According to Halo Surface Signal, Secret Server is a PAM solution frequently deployed as an internet-facing gateway for remote administration. If your instance is reachable over the internet, it is at higher risk. Even if hosted internally, any user or device with network access to the application's authentication page could potentially exploit this flaw.

What should I do to secure my environment?

The immediate priority is to identify all on-premise instances of Secret Server. Determine if these systems are reachable from the internet or sensitive networks. Once identified, work with your platform or security teams to restrict access where possible and prepare for an update, as instances prior to version 12.3.1 are affected.

References