CVE-2026-12587

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (14th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
8.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.6Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Spanish National Cybersecurity Institute, S.A. (INCIBE)) lists Resamania Virtuagym versions up to and including 21/08/2026 as affected. No release containing a fix is confirmed on record.

The vulnerability allows the unauthorised generation of physical access QR codes due to the use of hard-coded credentials within the application. The generation mechanism uses the 'badge_number' parameter as the HMAC private key, the value of which remains static and is accessible via the API using the endpoint '/club/_id_club_/member/_id_member_/resamania_qr_info'. An attacker with access to this value and to the application’s cryptographic logic, which can be extracted by reverse engineering the APK as there is no code obfuscation, could generate valid QR codes indefinitely, even after the user has changed their password or logged out.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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)
Severity86% × 45%
The EG Score, 8.6 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 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 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 26, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

Embedded credentials in Virtuagym | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/embedded-credentials-virtuagym

Vendor Advisories for CVE-2026-12587(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 17× in last 7d / 90× 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 156 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 56 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12587?
CVE-2026-12587 is a high-severity vulnerability; its CVE record was published on August 26, 2026. The vulnerability allows the unauthorised generation of physical access QR codes due to the use of hard-coded credentials within the application. The generation mechanism uses the 'badgenumber' parameter as the HMAC private key, the value of which remains static and is accessible via the API using…
When was CVE-2026-12587 made public?
CVE-2026-12587 was made public on August 21, 2026: that is the date its CVE record's CNA, Spanish National Cybersecurity Institute, S.A. (INCIBE), gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-12587 actively exploited?
CVE-2026-12587 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12587?
CVE-2026-12587 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12587?
No fix for CVE-2026-12587 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 CVE record's CNA (Spanish National Cybersecurity Institute, S.A. (INCIBE)) lists Resamania Virtuagym versions up to and including 21/08/2026 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-12587 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12587?

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

Book a Demo →Browse All CVEs