CVE-2026-12787

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-06-21. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: None knownExposed services: Not assessed

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

A vulnerability was found in zhilink 智互联(深圳)科技有限公司 ADP Application Developer Platform 应用开发者平台 1.0.0. This affects an unknown part of the component testConnection Endpoint. The manipulation of the argument jdbcUrl results in deserialization. The attack may be performed from remote. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)60 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's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 21, 2026

Last Modified

June 22, 2026

Vendor Advisories for CVE-2026-12787(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 25× 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 190 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 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-12787?
CVE-2026-12787 is a medium-severity vulnerability; its CVE record was published on June 21, 2026. A vulnerability was found in zhilink 智互联(深圳)科技有限公司 ADP Application Developer Platform 应用开发者平台 1.0.0. This affects an unknown part of the component testConnection Endpoint. The manipulation of the argument jdbcUrl results in deserialization. The attack may be performed from remote. The exploit has…
When was the CVE record for CVE-2026-12787 published?
The CVE record for CVE-2026-12787 was published on June 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 22, 2026; the record at its source may have been updated since.
Is CVE-2026-12787 actively exploited?
CVE-2026-12787 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12787?
CVE-2026-12787 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12787?
No fix for CVE-2026-12787 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 vendor advisories EchelonGraph has for CVE-2026-12787 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12787?

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