CVE-2026-47723

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.1, none of the response paths in internal/web/ or internal/api/ set the standard browser-security headers. grep for Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy returns zero matches across the codebase. Version 0.3.1 fixes the issue.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

June 8, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated Jul 24, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Web UI and API responses lack security headers (CSP, X-Frame-Options, HSTS, etc.) · Advisory · forgekeep/nebula-mesh · GitHub

https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-w7w5-5gcp-38rw
github_release Patch Available

v0.3.1

Patch available: forgekeep/nebula-mesh v0.3.1

https://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.1
github_commit

commit b45fda5476c4 (forgekeep/nebula-mesh)

Fix landed in forgekeep/nebula-mesh commit b45fda5476c4 — awaiting tagged release

https://github.com/forgekeep/nebula-mesh/commit/b45fda5476c41ffcff1ca23058aef0fb851359c1

Vendor Advisories for CVE-2026-47723(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/juev/nebula-mesh—0.3.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 21:38 UTCEG score recompute
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 07:08 UTCEG score recompute
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 20:24 UTCEG score recompute▲ 7.10
  7. 2026-07-23 20:21 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
  8. 2026-07-23 03:17 UTCEG score recompute
  9. 2026-06-14 23:18 UTCEPSS rescore
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-08 23:31 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47723?
CVE-2026-47723 is a high vulnerability published on June 8, 2026. nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.1, none of the response paths in internal/web/ or internal/api/ set the standard browser-security headers. grep for Content-Security-Policy, X-Frame-Options, Strict-Transport-Security,…
When was CVE-2026-47723 disclosed?
CVE-2026-47723 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47723 actively exploited?
CVE-2026-47723 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.5% of all scored CVEs.
What is the CVSS score of CVE-2026-47723?
CVE-2026-47723 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-47723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47723, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47723

Explore →

Is Your Infrastructure Affected by CVE-2026-47723?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs