Skip to content
Applications

CVE-2026-39911

8.7
High
EPSS 0.55%Apr 10, 2026

Auth users can run arbitrary Node.js code via unsandboxed JS in policy.

common questions

Is CVE-2026-39911 being exploited?

Not confirmed. CVE-2026-39911 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. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.

How severe is CVE-2026-39911?

CVE-2026-39911 is rated High with a CVSS score of 8.7. 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-39911?

Not known from our data. No patch reference has been recorded for CVE-2026-39911, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-39911 affect?

CVE-2026-39911 affects Hashgraph Guardian <= 3.5.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-39911?

Apply patch; disable unsandboxed Function() usage; limit privileges.

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

executive summary
technical analysis
affected
Hashgraph Guardian <= 3.5.0
impact

Authenticated RCE via unsandboxed JS; read files, access credentials, forge tokens including admin.

action required

Patch when possible

affected versions
hashgraph guardian
  • affected<= 3.5.1
vendor says fixed in45fbe2f7e0e8feee30105d42d66ed63fb6177ebe

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.

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
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free