CVE-2026-45178
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 · uneditedIdira Secrets Manager Self-Hosted versions 13.8.0 and lower exhibit improper access control within internal cluster endpoints. A remote, authenticated attacker possessing standard node-level credentials could leverage these endpoints to potentially retrieve unauthorized secrets or cause a denial of service (DoS). CyberArk Security Bulletin: CA26-20
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 · moderate confidenceIdira Secrets Manager Self-Hosted versions 13.8.0 and lower contain improper access control vulnerabilities in internal cluster endpoints. A remote, authenticated attacker with standard node-level credentials can exploit these misconfigured internal endpoints to retrieve secrets they should not have access to, or trigger denial of service conditions.
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>= 13.0, < 13.8.1>= 14.0, < 14.2.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Idira Secrets Manager versionCheck the version of the Idira Secrets Manager Self-Hosted installation using product-specific commands or configuration files (typically accessible via admin interface or command-line tools)Affected if The installed version is 13.0.0 through 13.8.0 (inclusive)
-
Identify installed Credential Provider versionCheck the version of any deployed Idira Secrets Manager Credential Providers using product-specific commands or configuration filesAffected if The installed version is 14.0.0 through 14.2.5 (inclusive)
-
Verify internal cluster endpoint accessibilityTest whether internal cluster endpoints are reachable using standard node-level authentication credentialsAffected if Internal endpoints respond to node-level credentials without requiring elevated privileges
-
Confirm node-level credential privilege boundariesAttempt to access secret retrieval functions using standard node-level credentials to verify if authorization controls are properly enforcedAffected if Node-level credentials can retrieve secrets outside their intended scope or access functions reserved for higher-privilege roles
A user is affected if they run Idira Secrets Manager versions 13.0-13.8.0 or Credential Provider versions 14.0-14.2.5, AND internal cluster endpoints are accessible with standard node-level credentials that can bypass authorization to access sensitive secrets.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data13.8.114.2.6
Upgrade to a patched version of Idira Secrets Manager Self-Hosted beyond 13.8.0, or implement strict network segmentation and authentication controls on internal cluster endpoints to prevent unauthorized access from standard node-level accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45178 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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