CVE-2026-86887

LOWPre-NVD 3.33.3
EchelonGraph scoreHIGH confidence

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

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-09-14. 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
Trending — 3 sources updated this week
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.2%CVSS: 3.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

A privacy issue was addressed by removing sensitive data. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, visionOS 27. An app may be able to bypass certain Privacy preferences.

CVSS v3
3.3
EG Score
3.3LOWhigh 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.
Exploitation0.2% × 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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

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

The CVE record names the fixed release. 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 14, 2026

Last Modified

September 21, 2026

References (3)

Vendor Advisories for CVE-2026-86887(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 14× in last 7d / 53× 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-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-12 14:50 UTCEG score recompute
  4. 2026-10-11 19:16 UTCEG score recompute
  5. 2026-10-11 16:33 UTCEG score recompute
  6. 2026-10-11 14:16 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  7. 2026-10-11 13:50 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-08 05:31 UTCEG score recompute
  13. 2026-10-08 05:31 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-04 22:25 UTCEG score recompute
  19. 2026-10-04 22:25 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-01 15:20 UTCEG score recompute
  22. 2026-10-01 15:20 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  23. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-28 08:15 UTCEG score recompute
Show 28 more
  1. 2026-09-28 08:15 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  2. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-09-25 01:11 UTCEG score recompute
  4. 2026-09-25 01:11 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  5. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-09-21 18:06 UTCEG score recompute
  10. 2026-09-21 18:06 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-09-20 01:02 UTCEG score recompute
  13. 2026-09-20 01:02 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  14. 2026-09-19 14:29 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  15. 2026-09-19 13:57 UTCEG score recompute
  16. 2026-09-19 13:57 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w · GitHub severity LOW · GitHub CVSS 3.3
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-17 15:29 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w
  20. 2026-09-17 14:49 UTCEG score recomputeFirst assessed: 3.3 LOW
  21. 2026-09-17 14:49 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w
  22. 2026-09-17 14:49 UTCMITRE cvelistV5CVSS v3 → 3.3 · severity → LOW
  23. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-15 14:58 UTCGHSA enrichmentGHSA-jp42-wwp7-m94w
  26. 2026-09-14 21:22 UTCNVD update
  27. 2026-09-14 20:58 UTCEG score recompute
  28. 2026-09-14 20:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86887?
CVE-2026-86887 is a low-severity vulnerability; its CVE record was published on September 14, 2026. A privacy issue was addressed by removing sensitive data. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, visionOS 27. An app may be able to bypass certain Privacy preferences.
When was the CVE record for CVE-2026-86887 published?
The CVE record for CVE-2026-86887 was published on September 14, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-86887 actively exploited?
CVE-2026-86887 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86887?
CVE-2026-86887 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-86887?
The CVE record for CVE-2026-86887 names the fix: "This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, visionOS 27." The vendor advisories EchelonGraph has for CVE-2026-86887 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-86887?

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

Book a Demo →Browse All CVEs