Idira Privilege Cloud ConnectorApplication · Paloaltonetworks
CVE-2026-45170
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 Vendor PAM - Self-Hosted Connector versions prior 1.1.100504 under specific conditions and configuration scenarios, TLS certificate validation may not be fully enforced. CyberArk Security Bulletin: CA26-17
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 Vendor PAM Self-Hosted Connector versions prior to 1.1.100504 fail to fully enforce TLS certificate validation under certain configuration scenarios, allowing potential man-in-the-middle attacks where an attacker could intercept encrypted communications between the connector and backend services.
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
Idira Privilege Cloud ConnectorApplication
>= 1.1.0, < 1.1.100504CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the installed connector versionLocate the Idira Vendor PAM Self-Hosted Connector (or Paloaltonetworks Idira Privilege Cloud Connector) installation and retrieve its version number from the product itself, its installer, or version metadata files. Common locations include the installation directory, About dialog, or service information.Affected if The installed version is 1.1.0 through 1.1.100503 (any version >= 1.1.0 but < 1.1.100504)
-
Verify TLS certificate validation configurationExamine the connector's configuration files, registry entries, or administrative interface settings related to TLS/SSL certificate validation. Look for settings that control certificate verification, trust validation, or SSL/TLS security options.Affected if TLS certificate validation is disabled, set to optional, or configured in a manner that allows incomplete validation (e.g., skipping certificate chain verification, hostname validation, or trust verification)
-
Check for configuration scenarios that bypass TLS validationReview the connector's connection profiles, endpoint configurations, or communication settings to identify any scenarios where TLS validation may be relaxed or overridden. Common areas include connector-to-server communication settings, proxy configurations, or legacy compatibility modes.Affected if The connector is configured with settings that permit connections without full certificate validation, such as trust-on-first-use, insecure mode, or certificate validation bypass options
A user is affected if the installed Idira Vendor PAM Self-Hosted Connector version is between 1.1.0 and 1.1.100503 AND TLS certificate validation is not fully enforced in the current configuration.
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.
dbcve · scoped1.1.100504
Upgrade Idira Vendor PAM Self-Hosted Connector to version 1.1.100504 or later to ensure proper TLS certificate validation is enforced.
1.1.100504 or later
- Identify the currently installed version of Idira Privilege Cloud Connector
- Plan an upgrade to version 1.1.100504 or later
- Review CyberArk's official upgrade documentation for Idira Privilege Cloud Connector
- Execute the upgrade following vendor-approved procedures
- After upgrade, verify that TLS certificate validation is properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Idira Privilege Cloud Connector
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45170 — 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-45170 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