Skip to content
Networks

CVE-2026-47722

8.7
High
EPSS 0.47%Patch availableJul 24, 2026

Server-side template injection in nebula-mesh allows malicious config/template execution.

common questions

Is CVE-2026-47722 being exploited?

Not confirmed. CVE-2026-47722 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.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-47722?

CVE-2026-47722 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-47722?

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

What does CVE-2026-47722 affect?

CVE-2026-47722 affects nebula-mesh < 0.3.2, self-hosted Slack Nebula control planes, agents using generated config.yml. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47722?

Upgrade to nebula-mesh 0.3.2, restrict admin access, validate inputs and review generated configs.

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

executive summary
technical analysis
affected
nebula-mesh < 0.3.2self-hosted Slack Nebula control planesagents using generated config.yml
impact

Server-side template injection via ListenHost/TunDevice enables arbitrary template execution, config manipulation, possible remote code execution and agent compromise.

action required

Immediate action required

affected versions
juev nebula-mesh
  • affected< 0.3.2

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