VYPR
Medium severity6.3NVD Advisory· Published Jun 1, 2026

CVE-2026-10240

CVE-2026-10240

Description

A server-side request forgery (SSRF) in JeecgBoot ≤3.9.2 allows any authenticated user to abuse the /airag/airagModel/test endpoint to probe internal networks or access cloud metadata.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A server-side request forgery (SSRF) in JeecgBoot ≤3.9.2 allows any authenticated user to abuse the /airag/airagModel/test endpoint to probe internal networks or access cloud metadata.

Vulnerability

A server-side request forgery (SSRF) vulnerability exists in JeecgBoot up to version 3.9.2 [1][2]. The affected endpoint is POST /airag/airagModel/test in AiragModelController.java. The baseUrl argument of the AiragModel request body is passed to the langchain4j framework without validation or sanitization, enabling outbound HTTP requests to arbitrary URLs controlled by the attacker. The endpoint lacks permission annotations, so any authenticated user can trigger the flaw [2].

Exploitation

An attacker must be authenticated to the JeecgBoot application [2]. The attacker sends a POST request to /airag/airagModel/test with a JSON body containing an AiragModel object where baseUrl points to an internal resource (e.g., http://169.254.169.254/latest/meta-data/ for cloud metadata). The server processes the request and issues an outbound HTTP call to that URL via langchain4j. The malicious configuration is also persisted to the database, enabling stored SSRF [2].

Impact

A successful attack allows the attacker to probe internal network services, perform port scanning, or access sensitive cloud instance metadata (such as AWS/GCP metadata endpoints) [2]. This can lead to information disclosure of internal infrastructure details or credentials, with the potential for further lateral movement.

Mitigation

A fix is planned for the upcoming release, but no patched version is available yet [1]. The vendor has acknowledged the issue and a fix is planned [2]. As of the latest version 3.9.2 (2026-04-30), no workaround is documented in the available references [1][2].

AI Insight generated on Jun 1, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

5

News mentions

0

No linked articles in our index yet.