Skip to content
major vulnerability· requires attention

Core OpenSSL PKCS#12 import vulnerability enabling RCE in a widely deployed crypto library; broad impact across many products and services.

Cryptography

CVE-2026-60038

8.6
High
EPSS n/aPatch available

Code injection in OpenSSL ImportPKCS12 enabling remote code execution.

exploited
No known exploitation not in CISA KEV as of our last sync
fix
Patch available see the advisory in the references
likelihood
No EPSS score yet
Published 10 Nov 2026Analysed here 10 Nov 2026CVSS scored by the publisher (CNA)
common questions

Is CVE-2026-60038 being exploited?

Not confirmed. CVE-2026-60038 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-60038?

CVE-2026-60038 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-60038?

Yes. A fix has been recorded for CVE-2026-60038. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60038 affect?

CVE-2026-60038 affects OpenSSL (ImportPKCS12), Applications using OpenSSL PKCS#12 import, Servers/services that import .p12 files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60038?

Restrict/disable PKCS#12 import, limit access, and apply OpenSSL vendor fixes when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenSSL (ImportPKCS12)Applications using OpenSSL PKCS#12 importServers/services that import .p12 files
impact

Authenticated high‑privileged remote attacker can inject code via ImportPKCS12, causing remote code execution and full system compromise.

action required

Immediate action required

affected versions
MB connect line mbCONNECT24
  • affected>= 2.0.0 and < 2.21.0
MB connect line mymbCONNECT24
  • affected>= 2.0.0 and < 2.21.0
Helmholz myREX24V2
  • affected>= 2.0.0 and < 2.21.0
Helmholz myREX24V2.virtual
  • affected>= 2.0.0 and < 2.21.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

  1. 10 Nov 2026Published
  2. 10 Nov 2026CVE record last updated · same day later
  3. 10 Nov 2026Analysed by vulneraibility.com · same day later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 2 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved