# CVE-2026-61743: Chartbrew: DNS Rebinding SSRF Bypass in Outbound Request Validation

> Authenticated users can bypass SSRF protections via DNS rebinding to access internal services and cloud metadata in Chartbrew.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-9537-vm84-j26f

## What is CVE-2026-61743?

CVE-2026-61743 is a medium-severity server-side request forgery vulnerability in chartbrew, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.2, Chartbrew's server/modules/safeRequest.js calls validateOutboundUrl() to resolve and validate a target hostname, but request-promise performs a separate DNS resolution for the actual connection. An authenticated user who can create or test API connections and controls the target DNS name can return a public address during validation and a private address during the request, bypassing the protections implemented by server/modules/outboundTargetPolicy.js. This DNS rebinding condition can expose internal services, localhost resources, or cloud metadata endpoints. This issue is fixed in version 5.2.2.

Weakness: CWE-350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

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


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

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

## Is CVE-2026-61743 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61743 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61743 is a medium-severity server-side request forgery vulnerability in chartbrew, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61743 exists.

Affected product: chartbrew. 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-61743/ (Markdown: https://insights.sbomify.com/CVE-2026-61743/index.md)
```

## Sources

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

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