Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes

Exploitation

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

CVSS

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

EPSS

• CVE-2023-41329: 0.63% estimated exploitation activity in the next 30 days; percentile 50.21 (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.

Impact The proxy mode of WireMock, can be protected by the network restrictions configuration, as documented in Preventing proxying to and recording from specific target addresses. These restrictions can be configured using the domain names, and in such a case the configuration is vulnerable to the DNS rebinding attacks. A similar patch was applied in WireMock 3.0.0-beta-15 for the WireMock Webhook Extensions. The root cause of the attack is a defect in the logic which allows for a race condition triggered by a DNS server whose address expires in between the initial validation and the outbound network request that might go to a domain that was supposed to be prohibited. Control over a DNS service is required to exploit this attack, so it has high execution complexity and limited impact. Affected versions - WireMock 3,x until 3.0.3 (security patch), on default settings in environments with access to the network - WireMock 2.x until 2.35.1 (security patch), on default settings in…

Published by the source

8 Sep 2023, 12:19 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pmxq-pj47-j8j4

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pmxq-pj47-j8j4

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

# Patch Next advisory brief: CVE-2023-41329

Advisory: Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio webhooks, proxy and recorder modes
IDs: CVE-2023-41329, GHSA-pmxq-pj47-j8j4
Record: https://patchnext.com/advisories/cve-2023-41329 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.wiremock:wiremock 3.0.3; com.github.tomakehurst:wiremock-jre8 2.35.1; com.github.tomakehurst:wiremock-jre8-standalone 2.35.1; org.wiremock:wiremock-standalone 3.0.3; wiremock 2.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wiremock:wiremock: affected < 3.0.3; fixed in 3.0.3
- Maven com.github.tomakehurst:wiremock-jre8: affected < 2.35.1; fixed in 2.35.1
- Maven com.github.tomakehurst:wiremock-jre8-standalone: affected < 2.35.1; fixed in 2.35.1
- Maven org.wiremock:wiremock-standalone: affected < 3.0.3; fixed in 3.0.3
- PyPI wiremock: affected < 2.6.1; fixed in 2.6.1

## Suggested inspection (read-only)
- Maven org.wiremock:wiremock: check the installed version with your package manager.
- Maven com.github.tomakehurst:wiremock-jre8: check the installed version with your package manager.
- Maven com.github.tomakehurst:wiremock-jre8-standalone: check the installed version with your package manager.
- Maven org.wiremock:wiremock-standalone: check the installed version with your package manager.
- `python -m pip show wiremock`: prints the installed version. Run with the environment that serves production active.

## 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 org.wiremock:wiremock, com.github.tomakehurst:wiremock-jre8, com.github.tomakehurst:wiremock-jre8-standalone, org.wiremock:wiremock-standalone, wiremock.
- 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-pmxq-pj47-j8j4 (OSV record GHSA-pmxq-pj47-j8j4 lists affected ranges: Maven org.wiremock:wiremock-standalone >=0 =0 =0 =0 =0 <2.6.1 (fixed))
- Verified: https://github.com/advisories/GHSA-pmxq-pj47-j8j4 (GitHub-reviewed advisory GHSA-pmxq-pj47-j8j4 lists affected ranges: Maven org.wiremock:wiremock-standalone >=0 =0 =0 =0 =0 <2.6.1)

Commands are suggestions: review each one before running it.