Skip to content
CVE-2026-126997: SSRF Vulnerability in JeecgBoot Exposed

CVE-2026-126997: SSRF Vulnerability in JeecgBoot Exposed

First seen 13 Nov 2026, 07:42 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 13, 2026 at 07:42 UTC
  • •CVE-2026-126997 allows unauthenticated SSRF attacks in JeecgBoot.
  • •Public proof-of-concept tools for exploitation are available.
  • •Internet-facing deployments are most at risk, especially with flow-run enabled.

A SSRF vulnerability, CVE-2026-126997, was disclosed on November 12, 2026, affecting JeecgBoot versions up to 3.9.6. The flaw resides in the flow-run endpoint, allowing unauthenticated attackers to manipulate requests and potentially access internal services. Public proof-of-concept (PoC) tools are available, enabling exploitation without authentication. The vulnerability allows attackers to control server-side requests, leading to credential theft and exposure of sensitive data. The vendor was contacted prior to disclosure but did not respond. Internet-facing deployments with flow-run enabled are particularly at risk. Administrators are urged to monitor unusual requests and implement access restrictions until a fix is confirmed.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-12
CVE-2026-126997 disclosed
The SSRF vulnerability in JeecgBoot was publicly disclosed, allowing for potential remote exploitation.
Sploitus
2026-11-13
Public PoC released
A proof-of-concept tool for exploiting the CVE was released, enabling unauthorized testing.
Sploitus
2026-11-13
Vendor unresponsive
The vendor was contacted prior to the disclosure but did not respond to inquiries regarding the vulnerability.
Redpacketsecurity

More articles in this cluster (7)

Following this threat?

Track CVE-2026-126997 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of JeecgBoot are affected?
JeecgBoot versions up to 3.9.6 are affected by CVE-2026-126997.
Is there an active exploit in the wild?
While public proof-of-concept tools exist, there is no confirmed active exploitation reported yet.
What should I do to mitigate this vulnerability?
Monitor for unusual requests to the flow-run endpoint and restrict access until a vendor-supported fix is confirmed.