CVE-2024-12289: Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the in

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2024-12289 is a medium-severity flaw (CVSS 5.9) affecting boundary. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the initialization of the Boundary controller, which may cause the Boundary server to terminate prematurely. Boundary is only vulnerable to this flaw during the initialization of the Boundary controller, which on average is measured in milliseconds during the Boundary startup process. This vulnerability, CVE-2024-12289, is fixed in Boundary Co

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-460, CWE-665
Published	2024-12-12
Last modified	2026-06-17

Publisher (CNA): HashiCorp Inc. · Vendor: hashicorp

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

Am I affected?

Timeline

2024-12-12 23:15 UTCPublished CVE record published
2026-06-17 06:59 UTCUpdated Record last modified

hashicorp boundary UPGRADE

Affected: >= 0.8.0 and < 0.16.4 · >= 0.17.0 and < 0.17.3 · >= 0.18.0 and < 0.18.2

Fixed in: 0.16.4, 0.17.3, 0.18.2

Safe to downgrade to: a release before 0.8.0

1. Check installed version

apt-cache policy boundary || rpm -q boundary || boundary --version

2. UPGRADE to 0.16.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade boundary

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade boundary

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 0.8.0 (Debian / Ubuntu)

apt-cache madison boundary sudo apt install boundary=<VERSION_BEFORE_0.8.0> sudo apt-mark hold boundary

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list boundary sudo dnf downgrade boundary-<VERSION_BEFORE_0.8.0> sudo dnf versionlock add boundary

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-2024-12289?

boundary: upgrade to 0.16.4, 0.17.3, 0.18.2. Exact commands for each OS are on this page.

Is CVE-2024-12289 being exploited?

CVE-2024-12289 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-2024-12289 affect?

CVE-2024-12289 affects boundary. Severity is medium (CVSS 5.9). Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the initialization of the Boundary controller, which may cause the Boundary server to terminate prematurely. Boundary is only vulnerable

How urgent is CVE-2024-12289?

Priority 34/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs