# CVE-2026-12587: Embedded credentials in Virtuagym


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-45xr-rwjr-28jc

## What is CVE-2026-12587?

CVE-2026-12587 is a high-severity vulnerability in Resamania Virtuagym, published on 26 Aug 2026. 

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-12587?


## How do I fix CVE-2026-12587?

No fix has been published for CVE-2026-12587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12587 being exploited?

There is no known exploitation of CVE-2026-12587 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12587 and fix it if it is affected.

What it is: CVE-2026-12587 is a high-severity vulnerability in Resamania Virtuagym, published on 26 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-12587 in the wild and no public exploit code.

Affected product: Resamania Virtuagym. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12587/ (Markdown: https://insights.sbomify.com/CVE-2026-12587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12587
- OSV: https://osv.dev/vulnerability/CVE-2026-12587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12587/
Summaries are generated and may contain mistakes; the official description above is the record.