CVE-2026-22063 CVE-2026-22063 eMudhra CA Certificate Compromise in NetApp Products
Medium 6.0
Published
Updated
Check this codebase for CVE-2026-22063 and fix it if it is affected.
What it is: CVE-2026-22063 is a medium-severity vulnerability in NetApp E-Series SANtricity OS Controller Software, published on 27 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-22063 in the wild and no public exploit code.
Affected product: NetApp E-Series SANtricity OS Controller Software. 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-22063/ (Markdown: https://insights.sbomify.com/CVE-2026-22063/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-22063?
CVE-2026-22063 is a medium-severity vulnerability in NetApp E-Series SANtricity OS Controller Software, published on 27 Oct 2026.
Official description
The private keys of eight eMudhra intermediate CA certificates have been compromised. eMudhra revoked the eight affected intermediate certificates on October 18, 2026. While this is not a software vulnerability, CVE-2026-22063 has been assigned to track relevant changes in impacted NetApp products.
Which versions are affected by CVE-2026-22063?
How do I fix CVE-2026-22063?
No fix has been published for CVE-2026-22063 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-22063 being exploited?
There is no known exploitation of CVE-2026-22063 in the wild and no public exploit code.
Sources
Also known as GHSA-433q-6ghj-2qwf.