Skip to main content
VulnerabilityPublished

CVE-2026-43993: Dragonmonk111 junoclaw · Server-Side Request Forgery (SSRF)

Affects Dragonmonk111 junoclawSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Dragonmonk111junoclawAffected
  • =< v0.x.y-security-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version 0.x.y-security-1 of junoclaw is available that addresses this SSRF vulnerability by validating the scheme, port, and resolved IP of URLs before fetching. Users should upgrade to this version to remediate the issue. Since this is not a cloud service, remediation depends on applying the vendor's fixed release. Patch status is not explicitly confirmed beyond the version note, so users should consult the vendor advisory or release notes for confirmation.

Description

JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, the WAVS bridge's computeDataVerify called fetch() on agent-supplied URLs without validating scheme, port, or resolved IP, resulting in an SSRF vulnerability. This vulnerability is fixed in 0.x.y-security-1.

References

Community reviews

Loading reviews…