CVE-2023-39347

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.6 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question. This can affect Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic, Cilium clusterwide network policies that use Cilium namespace labels to select the Pod and Kubernetes network policies. Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the io.kubernetes.pod.namespace label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question. This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users are advised to upgrade. As a workaround an admission webhook can be used to prevent pod label updates to the k8s:io.kubernetes.pod.namespace and io.cilium.k8s.policy.* keys.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 27, 2023

Last Modified

November 21, 2024

References (2)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/cilium/cilium—
  • 1.13.0 up to 1.13.7: fixed in 1.13.7
  • 1.14.0 up to 1.14.2: fixed in 1.14.2
  • every version up to 1.12.14: fixed in 1.12.14
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 85 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 100 are merged into the row they repeat. The 115 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-20 23:31 UTCEG score recompute
  4. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-18 07:54 UTCEG score recompute
  8. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-13 00:54 UTCOSV refresh
  14. 2026-10-12 18:21 UTCEG score recompute
  15. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-11 21:47 UTCEG score recompute
  17. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  25. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 45th percentile
Show 60 more
  1. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-09-30 16:28 UTCEG score recompute
  3. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  4. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  5. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  6. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  7. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-09-22 23:02 UTCOSV refresh
  12. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-09-03 17:46 UTCOSV refresh
  28. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  29. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  38. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  39. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  40. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  41. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  42. 2026-08-17 06:57 UTCOSV refresh
  43. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  44. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  45. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  46. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  47. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  48. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  49. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  50. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  51. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  52. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  53. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  54. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  55. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  56. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  57. 2026-08-02 01:36 UTCOSV refresh
  58. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  59. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  60. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.5% · 37th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-39347?
CVE-2023-39347 is a high-severity vulnerability; its CVE record was published on September 27, 2023. Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels…
When was the CVE record for CVE-2023-39347 published?
The CVE record for CVE-2023-39347 was published on September 27, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-39347 actively exploited?
CVE-2023-39347 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-39347?
CVE-2023-39347 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2023-39347?
A fix for CVE-2023-39347 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-39347

Explore →

Is Your Infrastructure Affected by CVE-2023-39347?

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

Book a Demo →Browse All CVEs