# CVE-2026-45177: Idira Secrets Manager SaaS Edge: Authentication Bypass of an internal validation mechanism


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-6x94-6f82-g4jw

## What is CVE-2026-45177?

CVE-2026-45177 is a critical vulnerability in CyberArk Software, a Palo Alto Networks Company Conjur Cloud (Edge Finding only), published on 11 Jun 2026. 

### Official description

Idira Secrets Manager SaaS Edge versions prior to 1.8 exhibit improper access control within its internal authentication components. A remote, unauthenticated attacker could exploit this by submitting a specially crafted request. Under specific circumstances, this could allow the attacker to manipulate internal validation mechanisms, potentially leading to a bypass of identity verification and the unauthorized acquisition of an access token. CyberArk Security Bulletin: CA26-20

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-45177?

It affects 1 product.


Products: Paloaltonetworks Idira Secrets Manager Edge.

## How do I fix CVE-2026-45177?

No fix has been published for CVE-2026-45177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45177 being exploited?

There is no known exploitation of CVE-2026-45177 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45177 and fix it if it is affected.

What it is: CVE-2026-45177 is a critical vulnerability in CyberArk Software, a Palo Alto Networks Company Conjur Cloud (Edge Finding only), published on 11 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-45177 in the wild and no public exploit code.

Affected product: CyberArk Software, a Palo Alto Networks Company Conjur Cloud (Edge Finding only). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45177/ (Markdown: https://insights.sbomify.com/CVE-2026-45177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45177
- OSV: https://osv.dev/vulnerability/CVE-2026-45177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45177/
Summaries are generated and may contain mistakes; the official description above is the record.