PatchTheCVECVE-2020-10993: Osmand through 2.0.0 allow XXE because of binary/BinaryMapIndexReader.java.
CVE-2020-10993 is a critical-severity flaw (CVSS 9.1) affecting osmand. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Osmand through 2.0.0 allow XXE because of binary/BinaryMapIndexReader.java.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.1 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.3% (top 30%) |
| CISA exploited list | No |
| Weakness | CWE-611 |
| Published | 2020-03-27 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-10993?
osmand: upgrade to newer than 2.0.0. Exact commands for each OS are on this page.
Is CVE-2020-10993 being exploited?
CVE-2020-10993 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-10993 affect?
CVE-2020-10993 affects osmand. Severity is critical (CVSS 9.1). Osmand through 2.0.0 allow XXE because of binary/BinaryMapIndexReader.java.
How urgent is CVE-2020-10993?
Priority 59/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action