Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker could, under specific conditions, attach their own FIDO2 credential to another user’s account and sign in as that user. Successful abuse could compromise privileged credentials and secrets managed by an affected on-premises Secret Server deployment. Cloud deployments are not identified as affected.
Executive priority
Treat affected on-premises deployments as an immediate remediation priority, especially where Secret Server protects privileged or business-critical credentials. Assign ownership today, reduce network exposure, review FIDO2 registrations, and follow Delinea’s current remediation guidance. There is no supplied evidence of active exploitation, but the potential consequence is full account impersonation.
Technical view
CVE-2026-19117 is an authentication bypass classified as CWE-290. It affects specified Delinea Secret Server on-premises versions and carries CVSS 3.1 score 9.8: network-accessible, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact. The sources do not describe the required conditions in detail.
Likely exposure
Exposure is limited to on-premises Secret Server versions 10.6.0, 11.8.0, 11.9.0, 12.0.0, and 12.1.0. Prioritize systems whose authentication or FIDO2 registration interfaces are network-accessible. The supplied record marks other versions as unaffected by default, but inventories should be verified against current vendor guidance.
Exploitation context
The supplied sources establish a remotely reachable authentication-bypass risk but do not report known active exploitation, public exploit availability, or inclusion in CISA KEV. Exploitation requires unspecified conditions, so absence of detail should not be interpreted as low exploitability.
Researcher notes
The record provides CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H and CWE-290. It does not disclose the prerequisite conditions, affected configuration details, detection indicators, fixed versions, or technical root cause. Validation should remain defensive and focus on version inventory, exposure, credential-registration history, and authentication anomalies.
Mitigation direction
- Identify all on-premises Secret Server instances and record their exact versions.
- Consult Delinea’s security advisory for the current fixed release or vendor-approved mitigation.
- Apply the vendor-provided update or mitigation as an emergency change after appropriate testing.
- Restrict network access to affected instances until vendor remediation is confirmed.
- Review and remove unauthorized FIDO2 credentials using approved administrative procedures.
Validation and detection
- Confirm whether each instance is on-premises and matches a listed affected version.
- Verify the installed version against Delinea’s current advisory after remediation.
- Review recent FIDO2 credential registrations for unexpected additions to sensitive accounts.
- Investigate suspicious authentication activity associated with newly registered FIDO2 credentials.
- Confirm access controls limit authentication and registration interfaces to intended networks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-19117 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9DelineaVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://delinea.com/security-advisoriesCVE reference, Delinea · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.