CVSS 4.0
5.5 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PCVE-2026-126997 JeecgBoot flow-run Endpoint a.class RestTemplate.exchange server-side request forgery
Medium (5.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
A vulnerability was identified in JeecgBoot up to 3.9.6. This affects the function RestTemplate.exchange of the file org/jeecg/modules/airag/flow/c/a.class of the component flow-run Endpoint. The manipulation leads to server-side request forgery. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
Severity
CVSS 3.1
7.3 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-918 Server-Side Request Forgery (SSRF)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- VulDB (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126997 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126997?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126997?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126997 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126997)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126997"><img src="https://cve.bz/cve/badge/CVE-2026-126997.svg" alt="CVE-2026-126997"></a>
GitHub PoC (unverified)
Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
- evenomn/CVE-2026-126997 0 stars, Python, created
Attack patterns (CAPEC)
- CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- Score 6.9 → 5.5 medium
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.