dbcve.org
Secret ServerApplication · Delinea

CVE-2025-12810

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Authentication vulnerability in Delinea Inc. Secret Server On-Prem (RPC Password Rotation modules).This issue affects Secret Server On-Prem: 11.8.1, 11.9.6, 11.9.25. A secret with "change password on check in" enabled automatically checks in even when the password change fails after reaching its retry limit. This leaves the secret in an inconsistent state with the wrong password. Remediation: Upgrade to 11.9.47 or later. The secret will remain checked out when the password change fails.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an improper authentication vulnerability in Delinea Secret Server On-Prem's RPC Password Rotation module where secrets configured with 'change password on check in' automatically check in even when password changes fail after exhausting retry limits, leaving the secret in an inconsistent state with an incorrect password stored.

MitigationUpgrade Secret Server On-Prem to version 11.9.47 or later, which ensures secrets remain checked out when password rotation fails, preventing inconsistent password states.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Secret ServerApplication
Affected:= 11.8.000001= 11.9.000006= 11.9.000025

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Secret Server version
    Access the Secret Server admin dashboard and navigate to Configuration > General or About page to view the exact version number (for example, Help > About in the application)
    Affected if The version displayed matches 11.8.000001, 11.9.000006, or 11.9.000025 exactly
  2. Locate secrets configured with password change on check-in
    In the Secret Server UI, search for secrets that have the 'Change Password on Check In' option enabled in their configuration (typically found in the Secret Template or individual Secret settings under Password Settings)
    Affected if Any secrets exist with 'Change Password on Check In' feature enabled
  3. Verify RPC Password Rotation is active
    Check the Secret Server configuration for any active Password Rotation schedules or RPC (Remote Password Changing) configurations that target the secrets with check-in password changes
    Affected if RPC Password Rotation is configured and actively running against secrets that have change-on-check-in enabled
  4. Review recent password rotation activity logs
    Examine Secret Server audit logs or password rotation logs for recent operations, looking for instances where password changes failed after exhausting retry limits
    Affected if Any password rotation attempts show failures after exhausting retry limits, leaving secrets checked in despite the failure

You are affected if your Secret Server version is exactly 11.8.000001, 11.9.000006, or 11.9.000025 AND you have secrets with 'Change Password on Check In' enabled using active RPC Password Rotation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Secret Server On-Prem to version 11.9.47 or later, which ensures secrets remain checked out when password rotation fails, preventing inconsistent password states.

Recommended fix High confidence

11.9.47 or later

  1. Obtain the Secret Server version 11.9.47 or later installer from Delinea's official distribution channels
  2. Review Delinea's upgrade documentation for Secret Server On-Prem prior to upgrading
  3. Back up the existing Secret Server database and configuration files
  4. Stop the Secret Server application services
  5. Install the upgraded version (11.9.47 or later) following Delinea's standard upgrade procedure
  6. Start the Secret Server application services
  7. Verify the upgrade was successful by checking the Secret Server version
  8. Confirm that secrets with 'change password on check in' enabled remain checked out when password change fails after reaching retry limit
Caveat Review Delinea's release notes for any configuration or behavioral changes between your current version and 11.9.47

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Secret Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12810 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data