# CVE-2026-43993: JunoClaw: SSRF in WAVS computeDataVerify allows cloud-metadata and internal-service access

> Attackers can exploit an SSRF vulnerability in JunoClaw to access cloud metadata and internal services via unvalidated agent-supplied URLs.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-q545-mvjf-q9pg

## What is CVE-2026-43993?

CVE-2026-43993 is a high-severity server-side request forgery vulnerability in Dragonmonk111 junoclaw, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-43993?


## How do I fix CVE-2026-43993?

No fix has been published for CVE-2026-43993 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-43993 being exploited?

There is no known exploitation of CVE-2026-43993 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43993 and fix it if it is affected.

What it is: CVE-2026-43993 is a high-severity server-side request forgery vulnerability in Dragonmonk111 junoclaw, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-43993 in the wild and no public exploit code.

Affected product: Dragonmonk111 junoclaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43993/ (Markdown: https://insights.sbomify.com/CVE-2026-43993/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43993
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43993
- OSV: https://osv.dev/vulnerability/CVE-2026-43993

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43993/
Summaries are generated and may contain mistakes; the official description above is the record.