npm package report

Is @utcp/http safe?

1 known vulnerability, worst severity MODERATE.

cvss
4.7

how bad it is if exploited, out of 10

epss
0.10%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-r8j5-8747-88cm, the advisory selected below

// advisories

GHSA-r8j5-8747-88cm

MODERATECVE-2026-45366

The @utcp/http package is vulnerable to a blind Server-Side Request Forgery (SSRF) caused by a trust-boundary inconsistency between manual discovery and tool invocation. registerManual() validates the discovery URL against an HTTPS / loopback allowlist, but callTool() reuses the resolved toolCallTemplate.url directly without revalidating, and the OpenApiConverter blindly trusts whatever servers[0]

Affected
>=0, <1.1.2, <= 1.1.1
Fixed in
1.1.2
Weakness
CWE-918
Published
2026-05-14
Source
osv

NVDMITREOSV

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 03:27 UTC. The most recent advisory here was published 2026-05-14. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @utcp/http safe? npm package security report | CyberXYZ