NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven🐍 PyPI
Not in CISA KEV
LOW severity

CVE-2023-41329 — wiremock-standalone

LOW

CVE-2023-41329 is a low-severity (CVSS 3.9) CWE-290 vulnerability in org.wiremock:wiremock-standalone. A fix is available for org.wiremock:wiremock-standalone — see the affected versions and patch details below.

Domain restrictions bypass via DNS Rebinding in WireMock and WireMock Studio

Also known asBIT-wiremock-2023-41329GHSA-pmxq-pj47-j8j4PYSEC-2026-2050
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-41329.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk
0.00%0.38%0.75%1.13%0.3%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected
☕org.wiremock:wiremock-standalone☕org.wiremock:wiremock☕com.github.tomakehurst:wiremock-jre8☕com.github.tomakehurst:wiremock-jre8-standalone🐍wiremock

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 environments with access to the network
  • Python WireMock until 2.6.1
  • WireMock Studio - all versions, this proprietary product was discontinued in 2022

Patches

  • WireMock 3.0.3 + the 3.0.3-1 Docker image
  • WireMock 2.35.1 + the 2.35.1-1 Docker image - backport to WireMock 2.x
  • Python WireMock 2.6.1

Workarounds

For WireMock:

  • Option 1: Configure WireMock to use IP addresses instead of the domain names in the outbound URLs subject to DNS rebinding
  • Option 2: Use external firewall rules to define the list of permitted destinations

For WireMock Studio: N/A. Switch to another distribution, there will be no fix provided. The vendor of former WireMock Studio recommends migration to WireMock Cloud

References

  • CVE-2023-41327 - Related issue in the WireMock Webhooks Extension

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.wiremock:wiremock-standaloneall versions3.0.3org.wiremock:wiremock-standalone:3.0.3
☕Mavenorg.wiremock:wiremockall versions3.0.3org.wiremock:wiremock:3.0.3
☕Mavencom.github.tomakehurst:wiremock-jre8all versions2.35.1com.github.tomakehurst:wiremock-jre8:2.35.1
☕Mavencom.github.tomakehurst:wiremock-jre8-standaloneall versions2.35.1com.github.tomakehurst:wiremock-jre8-standalone:2.35.1
🐍PyPIwiremockall versions2.6.1pip install --upgrade 'wiremock==2.6.1'

Affected Products

4 products · 6 configurations
Application
python wiremockwiremock
< 2.6.1
range
Application
studiowiremock
≤ 2.32.0-17
range
Application
wiremockwiremock
≥ 3.0.0 && < 3.0.3
range
Application
wiremock dockerwiremock
≥ 3.0.0 && < 3.0.3-1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wiremock:wiremock-standalone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.wiremock:wiremock-standalone to 3.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41329 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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](https://wiremock.org/docs/configuration/#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 f
O3 Security · Impact-Aware SCA

Is CVE-2023-41329 in your dependencies?

Find it across Maven, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-41329: wiremock-standalone — Fixed in 3.0.3