# CVE-2023-26735: Server-side request forgery in n/a

> Attackers can exploit the probe interface to scan intranet ports and download resources if authentication is not configured.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2023
- **Updated:** 9 Jul 2026
- **Also known as:** DEBIAN-CVE-2023-26735

## What is CVE-2023-26735?

CVE-2023-26735 is a high-severity server-side request forgery vulnerability in n/a, published on 25 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

blackbox_exporter v0.23.0 was discovered to contain an access control issue in its probe interface. This vulnerability allows attackers to detect intranet ports and services, as well as download resources. NOTE: this is disputed by third parties because authentication can be configured.

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

## Which versions are affected by CVE-2023-26735?

It affects 1 product.


Products: Prometheus Blackbox Exporter.

## How do I fix CVE-2023-26735?

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

## Is CVE-2023-26735 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-16248](https://insights.sbomify.com/CVE-2020-16248/): Server-side request forgery in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26735 and fix it if it is affected.

What it is: CVE-2023-26735 is a high-severity server-side request forgery vulnerability in n/a, published on 25 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26735 exists.

Affected product: n/a. 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-2023-26735/ (Markdown: https://insights.sbomify.com/CVE-2023-26735/index.md)
```

## Sources

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

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