CVE-2026-19000

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-53713 (ENISA EUVD) · GHSA-wwv2-c3p6-cpr5 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was identified in JeecgBoot up to 3.9.2." No release containing a fix is confirmed on record.

A vulnerability was identified in JeecgBoot up to 3.9.2. The affected element is an unknown function of the file /airag/chat/send of the component Anonymous Chat Attachment Parser. The manipulation leads to server-side request forgery. The attack can be initiated remotely. The exploit is publicly available and might be used. A fix is planned for the upcoming release.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
64
EG Risk 64/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)14 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

August 6, 2026

Last Modified

August 12, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
No fix on record yet.
Web page

GitHub - jeecgboot/JeecgBoot: 【低代码迈入v2.0时代,一句话即可生成整个系统】企业级AI低代码平台,一键生成前后端代码甚至整个系统。 AI Skills 一句话画流程、设计表单、生成报表、大屏。内置 AI应用平台涵盖:AI聊天、知识库、流程编排、MCP插件等,兼容主流大模型。引领AI低代码「Skills 生成 → 在线配置 → 代码生成 → 手工合并->AI修改」开发模式,解决 Java 项目 90% 重复工作...

GitHub - jeecgboot/JeecgBoot: 【低代码迈入v2.0时代,一句话即可生成整个系统】企业级AI低代码平台,一键生成前后端代码甚至整个系统。 AI Skills 一句话画流程、设计表单、生成报表、大屏。内置 AI应用平台涵盖:AI聊天、知识库、流程编排、MCP插件等,兼容主流大模型。引领AI低代码「Skills 生成 → 在线配置 → 代码生成 → 手工合并->AI修改」开发模式,解决 Java 项目 90% 重复工作,提高效率又不失灵活。 · GitHub

https://github.com/jeecgboot/JeecgBoot/
Web page

3.9.2版本 Airag 匿名聊天附件解析存在SSRF漏洞 · Issue #9672 · jeecgboot/JeecgBoot · GitHub

https://github.com/jeecgboot/JeecgBoot/issues/9672#issuecomment-4739323732
Web page

3.9.2版本 Airag 匿名聊天附件解析存在SSRF漏洞 · Issue #9672 · jeecgboot/JeecgBoot · GitHub

https://github.com/jeecgboot/JeecgBoot/issues/9672

Vendor Advisories for CVE-2026-19000(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 8× in last 7d / 36× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 273 rows 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 173 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-19000?
CVE-2026-19000 is a high-severity vulnerability; its CVE record was published on August 6, 2026. A vulnerability was identified in JeecgBoot up to 3.9.2. The affected element is an unknown function of the file /airag/chat/send of the component Anonymous Chat Attachment Parser. The manipulation leads to server-side request forgery. The attack can be initiated remotely. The exploit is publicly…
When was the CVE record for CVE-2026-19000 published?
The CVE record for CVE-2026-19000 was published on August 6, 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 August 12, 2026; the record at its source may have been updated since.
Is CVE-2026-19000 actively exploited?
CVE-2026-19000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19000?
CVE-2026-19000 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19000?
No fix for CVE-2026-19000 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 CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was identified in JeecgBoot up to 3.9.2." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-19000 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19000?

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