CVE-2026-0050

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

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

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-06-02. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
3.3EG
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.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed

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

In handleBondStateChanged of AdapterService.java, there is a possible sensitive information disclosure due to a permissions bypass. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100

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 (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
Exploitation<0.1% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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

June 1, 2026

Last Modified

July 22, 2026

References (1)

Vendor Advisories for CVE-2026-0050(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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. 4 repeat rows among the latest 72 are merged into the row they repeat.

  1. 2026-10-12 16:42 UTCEG score recompute
  2. 2026-10-11 20:17 UTCEG score recompute
  3. 2026-10-11 18:30 UTCEG score recompute
  4. 2026-10-11 15:03 UTCEG score recompute
  5. 2026-10-08 17:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-10-06 15:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-10-04 23:21 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-29 15:20 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-09-23 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-09-14 06:00 UTCEG score recompute
  11. 2026-09-14 06:00 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  12. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-09-10 09:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-09-04 05:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-09-01 04:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-08-25 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-08-23 13:47 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  18. 2026-08-20 10:14 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  19. 2026-08-16 02:21 UTCEG score recompute
  20. 2026-08-16 02:21 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  21. 2026-08-16 02:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-08-13 05:52 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  23. 2026-08-10 11:05 UTCEG score recompute
  24. 2026-08-10 11:05 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  25. 2026-08-08 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
Show 43 more
  1. 2026-08-07 16:42 UTCEG score recompute
  2. 2026-08-07 16:42 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  3. 2026-08-06 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-08-05 19:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-08-04 22:27 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  6. 2026-08-01 13:32 UTCEG score recompute
  7. 2026-08-01 13:32 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  8. 2026-08-01 04:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-07-30 16:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-07-29 17:25 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  11. 2026-07-26 23:09 UTCEG score recompute
  12. 2026-07-26 23:09 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  13. 2026-07-26 14:54 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-07-24 14:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-07-23 03:04 UTCEG score recompute
  16. 2026-07-14 13:09 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  17. 2026-07-11 13:21 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  18. 2026-07-08 16:50 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  19. 2026-07-08 15:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-07-07 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-07-02 08:24 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  22. 2026-06-29 14:08 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  23. 2026-06-29 14:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-06-26 19:52 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  25. 2026-06-24 01:37 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  26. 2026-06-23 21:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  27. 2026-06-18 16:53 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  28. 2026-06-17 17:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-06-15 17:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  30. 2026-06-15 16:56 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  31. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  32. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  33. 2026-06-12 22:40 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  34. 2026-06-11 14:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  35. 2026-06-10 13:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  36. 2026-06-10 04:25 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  37. 2026-06-07 15:24 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  38. 2026-06-07 10:09 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  39. 2026-06-05 22:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-06-04 15:54 UTCEG score recompute
  41. 2026-06-04 15:54 UTCGHSA enrichmentGHSA-22vw-7ch9-23fx · GitHub severity LOW · GitHub CVSS 3.3
  42. 2026-06-02 20:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-06-01 21:39 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-0050?
CVE-2026-0050 is a low-severity vulnerability; its CVE record was published on June 1, 2026. In handleBondStateChanged of AdapterService.java, there is a possible sensitive information disclosure due to a permissions bypass. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
When was the CVE record for CVE-2026-0050 published?
The CVE record for CVE-2026-0050 was published on June 1, 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 July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-0050 actively exploited?
CVE-2026-0050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0050?
CVE-2026-0050 has a CVSS v3.1 base score of 3.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0050?
No fix for CVE-2026-0050 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-0050 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0050

Explore →

Is Your Infrastructure Affected by CVE-2026-0050?

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