hemmelig allows SSRF Filter bypass via Secret Request functionality

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-69206: 0.20% estimated exploitation activity in the next 30 days; percentile 10.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) filter bypass vulnerability exists in the webhook URL validation of the Secret Requests feature. The application attempts to block internal/private IP addresses but can be bypassed using DNS rebinding (e.g., localtest.me which resolves to 127.0.0.1) or open redirect services (e.g., httpbin.org/redirect-to). This allows an authenticated user to make the server initiate HTTP requests to internal network resources. Details The vulnerability exists in the isPublicUrl function located in /api/lib/utils.ts. The function validates webhook URLs against a blocklist of private IP patterns: The validation is flawed because: 1. DNS Rebinding Bypass: It only checks the hostname string, not the resolved IP address. Domains like localtest.me pass validation (not matching any blocked pattern) but resolve to 127.0.0.1. 2. Open Redirect Bypass: External URLs like httpbin.org/redirect-to?url=http://127.0.0.1 pass validation since httpbin.org is a public…

Published by the source

29 Dec 2025, 21:31 UTC

Last modified by the source

29 Dec 2025, 21:35 UTC

Source last checked

26 Oct 2026, 12:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-vvxf-wj5w-6gj5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-vvxf-wj5w-6gj5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-69206

Advisory: hemmelig allows SSRF Filter bypass via Secret Request functionality
IDs: CVE-2025-69206, GHSA-vvxf-wj5w-6gj5
Record: https://patchnext.com/advisories/cve-2025-69206 (revision 2, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hemmelig 7.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hemmelig: affected < 7.3.3; fixed in 7.3.3

## Suggested inspection (read-only)
- `npm ls hemmelig --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hemmelig.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vvxf-wj5w-6gj5 (OSV record GHSA-vvxf-wj5w-6gj5 lists affected ranges: npm hemmelig >=0 <7.3.3 (fixed))
- Verified: https://github.com/advisories/GHSA-vvxf-wj5w-6gj5 (GitHub-reviewed advisory GHSA-vvxf-wj5w-6gj5 lists affected ranges: npm hemmelig >=0 <7.3.3)

Commands are suggestions: review each one before running it.