CVE-2025-56608

MEDIUMNVD 4.24.2—Trending — 3 sources updated this weekElevated

4.2

The SourceCodester Android application "Corona Virus Tracker App India" 1.0 uses MD5 for digest authentication in OkHttpClientWrapper.java. The handleDigest() function employs MessageDigest.getInstance("MD5") to hash credentials. MD5 is a broken cryptographic algorithm known to allow hash collisions. This makes the authentication mechanism vulnerable to replay, spoofing, or brute-force attacks, potentially leading to unauthorized access. The vulnerability corresponds to CWE-327 and aligns with OWASP M5: Insufficient Cryptography and MASVS MSTG-CRYPTO-4.

CVSS v3: 4.2
EG Score: 4.2(medium)
EPSS: 11.4%
KEV: Not listed

Published

September 3, 2025

Last Modified

September 8, 2025

References (3)

Weakness Classification(1)

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

CWE-290Authentication Bypass by Spoofing

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 23:31 UTCEG score recompute
2026-05-29 23:31 UTCGHSA enrichment
2026-05-29 13:44 UTCepss_batch

Frequently asked(5)

What is CVE-2025-56608?

CVE-2025-56608 is a medium vulnerability published on September 3, 2025. The SourceCodester Android application "Corona Virus Tracker App India" 1.0 uses MD5 for digest authentication in OkHttpClientWrapper.java. The handleDigest() function employs MessageDigest.getInstance("MD5") to hash credentials. MD5 is a broken cryptographic algorithm known to allow hash…

When was CVE-2025-56608 disclosed?

CVE-2025-56608 was first published in the National Vulnerability Database on September 3, 2025, with the most recent update on September 8, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2025-56608 actively exploited?

CVE-2025-56608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2025-56608?

CVE-2025-56608 has a CVSS v3 base score of 4.2 (NVD).

How do I remediate CVE-2025-56608?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-56608, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-56608

Explore →

Is Your Infrastructure Affected by CVE-2025-56608?

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

Start Free Scan →Browse All CVEs

CVE-2025-56608

📅 Published

🔄 Last Modified

🔗 References (3)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2025-56608?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (3)

Frequently asked(5)

Related CVEs(same CWE)