CVE-2026-25600

MEDIUMNVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

Score 6.4 from GitHub Security Advisory published 2026-06-01. NVD baseline CVSS 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.4Exploit: NoneExposed: 0

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

The PDBM application relies on a static, hard‑coded secret embedded in the PDBM.exe executable. This secret is used by the application’s encryption routines, including the function responsible for decrypting credentials stored in the product’s configuration file. Because the secret is constant across installations, any attacker with sufficient local privileges can extract it from the binary. Once obtained, the secret allows the attacker to decrypt the stored password and authenticate as the user defined in the configuration file. In the affected version, this user account is configured with administrative privileges, granting full access to PDBM’s management interface and its underlying operational functions.

CVSS v3
6.4
EG Score
6.4(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.0%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

CVE-2026-25600 — Credential Exposure Vulnerability in Trac PDBM - SI CERT

https://www.cert.si/en/cve-2026-25600/

Vendor Advisories for CVE-2026-25600(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 2× in last 7d / 17× 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.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 03:07 UTCEG score recompute
  3. 2026-07-16 01:36 UTCGHSA enrichment
  4. 2026-07-14 05:54 UTCGHSA enrichment
  5. 2026-07-11 13:43 UTCGHSA enrichment
  6. 2026-07-08 17:03 UTCGHSA enrichment
  7. 2026-07-08 15:15 UTCEPSS rescore
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-02 02:26 UTCGHSA enrichment
  11. 2026-07-01 00:45 UTCGHSA enrichment
  12. 2026-06-29 16:00 UTCGHSA enrichment
  13. 2026-06-28 17:43 UTCGHSA enrichment
  14. 2026-06-27 19:17 UTCGHSA enrichment
  15. 2026-06-26 21:01 UTCGHSA enrichment
  16. 2026-06-25 22:46 UTCGHSA enrichment
  17. 2026-06-25 00:27 UTCGHSA enrichment
  18. 2026-06-24 02:12 UTCGHSA enrichment
  19. 2026-06-18 04:04 UTCGHSA enrichment
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-17 17:53 UTCEPSS rescore
  22. 2026-06-17 05:48 UTCGHSA enrichment
  23. 2026-06-16 17:52 UTCEPSS rescore
  24. 2026-06-16 07:33 UTCGHSA enrichment
  25. 2026-06-15 17:48 UTCEPSS rescore
Show 39 more
  1. 2026-06-15 09:18 UTCGHSA enrichment
  2. 2026-06-14 23:18 UTCEPSS rescore
  3. 2026-06-14 10:42 UTCGHSA enrichment
  4. 2026-06-13 23:00 UTCEPSS rescore
  5. 2026-06-13 12:27 UTCGHSA enrichment
  6. 2026-06-12 23:12 UTCEPSS rescore
  7. 2026-06-12 23:12 UTCEPSS rescore
  8. 2026-06-12 14:08 UTCGHSA enrichment
  9. 2026-06-11 15:53 UTCGHSA enrichment
  10. 2026-06-11 14:00 UTCEPSS rescore
  11. 2026-06-10 22:18 UTCEPSS rescore
  12. 2026-06-10 22:18 UTCEPSS rescore
  13. 2026-06-10 17:36 UTCGHSA enrichment
  14. 2026-06-10 13:22 UTCEPSS rescore
  15. 2026-06-09 19:21 UTCGHSA enrichment
  16. 2026-06-08 21:05 UTCGHSA enrichment
  17. 2026-06-08 14:17 UTCEPSS rescore
  18. 2026-06-08 14:17 UTCEPSS rescore
  19. 2026-06-07 22:50 UTCGHSA enrichment
  20. 2026-06-07 15:25 UTCEPSS rescore
  21. 2026-06-07 15:25 UTCEPSS rescore
  22. 2026-06-07 15:25 UTCEPSS rescore
  23. 2026-06-07 00:35 UTCGHSA enrichment
  24. 2026-06-06 02:19 UTCGHSA enrichment
  25. 2026-06-05 22:47 UTCEPSS rescore
  26. 2026-06-05 22:47 UTCEPSS rescore
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-05 06:10 UTCEPSS rescore
  29. 2026-06-05 04:04 UTCGHSA enrichment
  30. 2026-06-04 13:12 UTCEPSS rescore
  31. 2026-06-04 13:12 UTCEPSS rescore
  32. 2026-06-04 05:49 UTCGHSA enrichment
  33. 2026-06-03 07:34 UTCGHSA enrichment
  34. 2026-06-02 20:13 UTCEPSS rescore
  35. 2026-06-02 20:13 UTCEPSS rescore
  36. 2026-06-02 09:18 UTCGHSA enrichment
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-06-01 11:03 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-25600?
CVE-2026-25600 is a medium vulnerability published on June 1, 2026. The PDBM application relies on a static, hard‑coded secret embedded in the PDBM.exe executable. This secret is used by the application’s encryption routines, including the function responsible for decrypting credentials stored in the product’s configuration file. Because the secret is constant…
When was CVE-2026-25600 disclosed?
CVE-2026-25600 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25600 actively exploited?
CVE-2026-25600 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25600?
CVE-2026-25600 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-25600?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25600, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-25600?

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

Start Free Scan →Browse All CVEs