Security readout for executives and security teams
Plain-English summary
CVE-2026-3270 is a server-side request forgery issue in PSI Probe’s Whois lookup feature. An authenticated remote user may be able to make the server send unintended requests. Public proof-of-concept material is referenced, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term remediation item for any exposed PSI Probe deployment. It is not currently supported as actively exploited, but public PoC availability and administrative-server placement justify prompt review and access tightening.
Technical view
The issue affects psi-probe PSI Probe versions 5.0, 5.1, 5.2, and 5.3.0. VulDB maps it to CWE-918 in psi-probe-core/src/main/java/psiprobe/tools/Whois.java, function lookup. CVSS v2 is 6.5 with network access, low complexity, and authentication required.
Likely exposure
Exposure is most likely where PSI Probe 5.0 through 5.3.0 is deployed and the Whois component is reachable by authenticated users. Internet-facing administrative deployments carry higher business risk.
Exploitation context
The source bundle says exploit details were publicly disclosed and may be used. However, KEV is false and no cited source confirms active exploitation in the wild. Authentication is listed as required.
Researcher notes
Evidence is limited to CVE/VulDB records and a referenced public GitHub issue. No vendor response or patch is cited in the provided sources. Avoid assuming affected versions beyond 5.0, 5.1, 5.2, and 5.3.0.
Mitigation direction
- Identify PSI Probe instances and confirm whether versions 5.0 through 5.3.0 are in use.
- Check PSI Probe vendor or project guidance for an official fix or workaround.
- Limit PSI Probe access to trusted administrative networks and users.
- Review whether the Whois feature is needed and reduce exposure where possible.
- Monitor logs for unusual Whois lookups or unexpected outbound requests from PSI Probe hosts.
Validation and detection
- Confirm deployed PSI Probe version from asset inventory or application metadata.
- Verify whether the Whois component is enabled or reachable.
- Check access controls for PSI Probe administrative interfaces.
- Review outbound network logs from PSI Probe servers for unexpected destinations.
- Track vendor, CVE, and VulDB pages for updated remediation information.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3270 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-347994 | psi-probe PSI Probe Whois Whois.java lookup server-side request forgeryCVE reference · vdb-entry, technical-description
- VDB-347994 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #758666 | Psi Probe <=5.3.0 Server-Side Request ForgeryCVE reference · third-party-advisory
- https://github.com/AnalogyC0de/public_exp/issues/12CVE reference · exploit, issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.