CVE-2026-46370

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-06-12. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-66667 (ENISA EUVD) · GHSA-vxm7-9x8v-8gm4 (GitHub Security Advisories) · GO-2026-5682 (OSV.dev)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fleet is an open-source device management platform built on osquery. In versions up to and including 4.84.1, the labels host-listing endpoint (GET /api/v1/fleet/labels/{id}/hosts) allowed an authenticated user with the lowest-privilege Observer role to extract host enrollment secrets through a sort-order oracle. The endpoint accepted a user-supplied order_key parameter that was not validated against a column allowlist, so an attacker with Global or Team Observer access could set the sort column to a sensitive field such as h.node_key and combine it with the cursor-based after parameter to binary-search the value one character at a time; the targeted value never appeared in the response, but the presence or absence of results revealed each character. Because node_key and orbit_node_key are the long-lived shared secrets that osquery and Orbit agents use to authenticate to the Fleet server, an attacker who reconstructed them could impersonate enrolled hosts, submit fabricated query results and inventory, retrieve pending scripts and MDM commands, and poison compliance and policy results across the deployment. This issue is fixed in version 4.84.2.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
31st
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

June 12, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Aug 26, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint · Advisory · fleetdm/fleet · GitHub

https://github.com/fleetdm/fleet/security/advisories/GHSA-vxm7-9x8v-8gm4

Vendor Advisories for CVE-2026-46370(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/fleetdm/fleet/v4 @ 4.84.2 (fixes <= 4.84.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/fleetdm/fleet/v4—
  • every version up to 4.84.2: fixed in 4.84.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46370?
CVE-2026-46370 is a medium-severity vulnerability; its CVE record was published on June 12, 2026. Fleet is an open-source device management platform built on osquery. In versions up to and including 4.84.1, the labels host-listing endpoint (GET /api/v1/fleet/labels/{id}/hosts) allowed an authenticated user with the lowest-privilege Observer role to extract host enrollment secrets through a…
When was the CVE record for CVE-2026-46370 published?
The CVE record for CVE-2026-46370 was published on June 12, 2026. 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-46370 actively exploited?
CVE-2026-46370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46370?
CVE-2026-46370 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46370?
A fix for CVE-2026-46370 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46370 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46370?

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

Book a Demo →Browse All CVEs