2026.7.1
6 months ago
1 months ago
Known vulnerabilities in the @openclaw/nostr package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
@openclaw/nostr is an OpenClaw Nostr channel plugin for NIP-04 encrypted DMs Affected versions of this package are vulnerable to Incorrect Authorization through the How to fix Incorrect Authorization? Upgrade | <2026.5.2 |
@openclaw/nostr is an OpenClaw Nostr channel plugin for NIP-04 encrypted DMs Affected versions of this package are vulnerable to Information Exposure in the How to fix Information Exposure? Upgrade | <2026.5.2 |
@openclaw/nostr is an OpenClaw Nostr channel plugin for NIP-04 encrypted DMs Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the URL ingestion process. An attacker can access internal or private network resources by crafting a URL containing an ISATAP IPv6 literal that embeds a private IPv4 address, thereby bypassing hostname/IP filtering in URL-fetching paths. How to fix Server-side Request Forgery (SSRF)? Upgrade | <2026.2.19 |
@openclaw/nostr is an OpenClaw Nostr channel plugin for NIP-04 encrypted DMs Affected versions of this package are vulnerable to Authentication Bypass Using an Alternate Path or Channel via the Telegram webhook endpoint when webhook mode is enabled without a configured secret. An attacker can impersonate authorized users and execute privileged commands by sending forged HTTP POST requests with spoofed fields in the update payload. Note: This is only exploitable if the Telegram webhook is enabled and no webhook secret is configured. How to fix Authentication Bypass Using an Alternate Path or Channel? Upgrade | <2026.2.13 |