Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-41329: WireMock is a tool for mocking HTTP services

31
Routine
LOW 3.9WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2023-41329 is a low-severity flaw (CVSS 3.9) affecting python wiremock, studio, wiremock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

WireMock is a tool for mocking HTTP services. 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 Extension

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score3.9 (Low)
Attack vectorAdjacent network
Attack complexityHigh
Privileges neededHigh
User interactionNone
EPSS exploit chance0.6% (top 50%)
CISA exploited listNo
WeaknessCWE-290
Published2023-09-06
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: wiremock

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

wiremock python wiremock UPGRADE
Affected: < 2.6.1
Fixed in: 2.6.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy python-wiremock || rpm -q python-wiremock || python-wiremock --version
2. UPGRADE to 2.6.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade python-wiremock
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade python-wiremock
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
wiremock studio UPGRADE
Affected: <= 2.32.0-17
Fixed in: newer than 2.32.0-17
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy studio || rpm -q studio || studio --version
2. UPGRADE to newer than 2.32.0-17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade studio
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade studio
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
wiremock wiremock UPGRADE
Affected: < 2.35.1 · >= 3.0.0 and < 3.0.3
Fixed in: 2.35.1, 3.0.3
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy wiremock || rpm -q wiremock || wiremock --version
2. UPGRADE to 2.35.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade wiremock
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade wiremock
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison wiremock sudo apt install wiremock=<VERSION_BEFORE_3.0.0> sudo apt-mark hold wiremock
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list wiremock sudo dnf downgrade wiremock-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add wiremock
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wiremock wiremock docker UPGRADE
Affected: >= 2.0.0 and < 2.35.1-1 · >= 3.0.0 and < 3.0.3-1
Fixed in: 2.35.1-1, 3.0.3-1
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy wiremock-docker || rpm -q wiremock-docker || wiremock-docker --version
2. UPGRADE to 2.35.1-1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade wiremock-docker
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade wiremock-docker
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison wiremock-docker sudo apt install wiremock-docker=<VERSION_BEFORE_2.0.0> sudo apt-mark hold wiremock-docker
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list wiremock-docker sudo dnf downgrade wiremock-docker-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add wiremock-docker
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-41329?

python wiremock: upgrade to 2.6.1; studio: upgrade to newer than 2.32.0-17; wiremock: upgrade to 2.35.1, 3.0.3. Exact commands for each OS are on this page.

Is CVE-2023-41329 being exploited?

CVE-2023-41329 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-41329 affect?

CVE-2023-41329 affects python wiremock, studio, wiremock. Severity is low (CVSS 3.9). WireMock is a tool for mocking HTTP services. 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 c

How urgent is CVE-2023-41329?

Priority 31/100. On your watchlist

Software pages

Python vulnerabilities · Docker vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.