# CVE-2026-3270: psi-probe PSI Probe Whois Whois.java lookup server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in PSI Probe's Whois lookup function to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 26 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-429m-9874-rx9w

## What is CVE-2026-3270?

CVE-2026-3270 is a medium-severity server-side request forgery vulnerability in psi-probe PSI Probe, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in psi-probe PSI Probe up to 5.3.0. This affects the function lookup of the file psi-probe-core/src/main/java/psiprobe/tools/Whois.java of the component Whois. The manipulation leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

2 open source packages ship an affected version, including com.github.psi-probe:psi-probe-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.psi-probe:psi-probe-core` | Maven | All versions to 5.3.0 | None |
| `com.github.psi-probe:psi-probe-core` | Maven | All versions to 5.3.0 | None |

Products: Psi-Probe Psi Probe.

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

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

## Is CVE-2026-3270 being exploited?

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

## Other vulnerabilities in psi-probe PSI Probe

- [CVE-2026-3268](https://insights.sbomify.com/CVE-2026-3268/): psi-probe PSI Probe Session Attribute RemoveSessAttributeController.java access control (medium 5.3)
- [CVE-2026-3269](https://insights.sbomify.com/CVE-2026-3269/): psi-probe PSI Probe Session ExpireSessionsController.java handleRequestInternal denial of service (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3270 is a medium-severity server-side request forgery vulnerability in psi-probe PSI Probe, published on 26 Feb 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-3270 exists.

Affected packages and fixed versions:
- com.github.psi-probe:psi-probe-core (Maven): affected all versions up to 5.3.0; no fix listed
- com.github.psi-probe:psi-probe-core (Maven): affected all versions up to 5.3.0; no fix listed

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

## Sources

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

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