CVE-2026-26897

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; 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 weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

An issue in EcoOnline EHS (com.airsweb.v10) application for Android, version 0.2.499 allows a remote attacker to obtain sensitive information and execute arbitrary code via the AndroidManifest.xml component

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.1%
EPSS %ILE
64th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

August 27, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. No fix on record yet.
Web pageMentions a patch (unverified)🟡 PoC Available

GitHub - iwallplace/CVE-2026-26897-EcoOnline-DeepLink: Public advisory & PoC for CVE-2026-26897 — Deep Link Bypass in EcoOnline EHS Android (com.airsweb.v10), fixed in 0.2.500 · GitHub

https://github.com/iwallplace/CVE-2026-26897-EcoOnline-DeepLink

Vendor Advisories for CVE-2026-26897(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 20× in last 7d / 162× 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 100 of 326 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. None are among the latest 100 rows. The 226 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 21:07 UTCEG score recompute
  2. 2026-10-19 21:07 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  4. 2026-10-18 19:59 UTCEG score recompute
  5. 2026-10-18 19:59 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  7. 2026-10-18 03:51 UTCEG score recompute
  8. 2026-10-17 19:38 UTCEG score recompute
  9. 2026-10-17 19:38 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  11. 2026-10-16 19:17 UTCEG score recompute
  12. 2026-10-16 19:17 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-16 16:41 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  14. 2026-10-15 16:44 UTCEG score recompute
  15. 2026-10-15 16:44 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  17. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  18. 2026-10-14 10:46 UTCEG score recompute
  19. 2026-10-14 10:46 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  21. 2026-10-13 09:16 UTCEG score recompute
  22. 2026-10-13 09:16 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  24. 2026-10-12 16:18 UTCEG score recompute
  25. 2026-10-12 08:54 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-11 20:00 UTCEG score recompute
  2. 2026-10-11 17:13 UTCEG score recompute
  3. 2026-10-11 14:45 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  6. 2026-10-10 14:10 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-10 09:52 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-10 05:48 UTCEG score recompute
  9. 2026-10-10 05:48 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  11. 2026-10-09 07:18 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-09 03:14 UTCEG score recompute
  13. 2026-10-09 03:14 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  15. 2026-10-08 08:44 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-08 05:05 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-08 01:26 UTCEG score recompute
  18. 2026-10-08 01:26 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  20. 2026-10-07 09:55 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-07 05:50 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-07 02:11 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-06 22:20 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-06 18:38 UTCEG score recompute
  25. 2026-10-06 18:38 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  27. 2026-10-06 14:59 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-06 11:13 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-06 07:34 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-06 00:57 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-05 20:32 UTCEG score recompute
  32. 2026-10-05 20:32 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  34. 2026-10-05 16:53 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-05 11:20 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-05 07:24 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-05 03:44 UTCEG score recompute
  38. 2026-10-05 03:44 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  40. 2026-10-04 23:20 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-04 19:40 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-04 13:22 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-04 09:15 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-04 05:35 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-04 01:56 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-03 19:42 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-03 16:03 UTCEG score recompute
  48. 2026-10-03 16:03 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  50. 2026-10-03 04:53 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-03 01:10 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-02 21:31 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-02 17:42 UTCEG score recompute
  54. 2026-10-02 17:42 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-02 14:02 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-02 09:58 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-02 06:20 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-02 01:14 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-01 19:54 UTCEG score recompute
  60. 2026-10-01 19:54 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  62. 2026-10-01 12:50 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-01 09:10 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-01 05:32 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-01 01:01 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-30 19:57 UTCEG score recompute
  67. 2026-09-30 19:57 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  69. 2026-09-30 08:52 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-30 05:13 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-29 16:09 UTCEG score recompute
  72. 2026-09-29 16:09 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-29 12:22 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-29 08:43 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-29 05:04 UTCGHSA enrichmentGHSA-2pvm-92qx-mc83 · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2026-26897?
CVE-2026-26897 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. An issue in EcoOnline EHS (com.airsweb.v10) application for Android, version 0.2.499 allows a remote attacker to obtain sensitive information and execute arbitrary code via the AndroidManifest.xml component
When was the CVE record for CVE-2026-26897 published?
The CVE record for CVE-2026-26897 was published on August 27, 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 1, 2026; the record at its source may have been updated since.
Is CVE-2026-26897 actively exploited?
CVE-2026-26897 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26897?
CVE-2026-26897 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-26897?
No fix for CVE-2026-26897 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-26897 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-26897?

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