CVE-2020-26230

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 1.7% (75th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.7%CVSS: 7.4Exploit: None knownExposed services: Not assessed

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

Radar COVID is the official COVID-19 exposure notification app for Spain. In affected versions of Radar COVID, identification and de-anonymization of COVID-19 positive users that upload Radar COVID TEKs to the Radar COVID server is possible. This vulnerability enables the identification and de-anonymization of COVID-19 positive users when using Radar COVID. The vulnerability is caused by the fact that Radar COVID connections to the server (uploading of TEKs to the backend) are only made by COVID-19 positives. Therefore, any on-path observer with the ability to monitor traffic between the app and the server can identify which users had a positive test. Such an adversary can be the mobile network operator (MNO) if the connection is done through a mobile network, the Internet Service Provider (ISP) if the connection is done through the Internet (e.g., a home network), a VPN provider used by the user, the local network operator in the case of enterprise networks, or any eavesdropper with access to the same network (WiFi or Ethernet) as the user as could be the case of public WiFi hotspots deployed at shopping centers, airports, hotels, and coffee shops. The attacker may also de-anonymize the user. For this additional stage to succeed, the adversary needs to correlate Radar COVID traffic to other identifiable information from the victim. This could be achieved by associating the connection to a contract with the name of the victim or by associating Radar COVID traffic to other user-generated flows containing identifiers in the clear (e.g., HTTP cookies or other mobile flows sending unique identifiers like the IMEI or the AAID without encryption). The former can be executed, for instance, by the Internet Service Provider or the MNO. The latter can be executed by any on-path adversary, such as the network provider or even the cloud provider that hosts more than one service accessed by the victim. The farther the adversary is either from the victim (the client) or the end-point (the server), the less likely it may be that the adversary has access to re-identification information. The vulnerability has been mitigated with the injection of dummy traffic from the application to the backend. Dummy traffic is generated by all users independently of whether they are COVID-19 positive or not. The issue was fixed in iOS in version 1.0.8 (uniform distribution), 1.1.0 (exponential distribution), Android in version 1.0.7 (uniform distribution), 1.1.0 (exponential distribution), Backend in version 1.1.2-RELEASE. For more information see the referenced GitHub Security Advisory.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

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
Severity74% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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.7%
EPSS %ILE
75th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

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 none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 13, 2020

Last Modified

November 21, 2024

References (24)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2020-26230?
CVE-2020-26230 is a high vulnerability published on November 13, 2020. Radar COVID is the official COVID-19 exposure notification app for Spain. In affected versions of Radar COVID, identification and de-anonymization of COVID-19 positive users that upload Radar COVID TEKs to the Radar COVID server is possible. This vulnerability enables the identification and…
When was CVE-2020-26230 disclosed?
CVE-2020-26230 was first published on November 13, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-26230 actively exploited?
CVE-2020-26230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% probability of exploitation in the next 30 days (75th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-26230?
CVE-2020-26230 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2020-26230?
No fix for CVE-2020-26230 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.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-26230

Explore →

Is Your Infrastructure Affected by CVE-2020-26230?

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