CVE-2026-46459
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedICU Scandinavia Boomerang is vulnerable to a missing authentication flaw in its device receiver endpoints. This allows an unauthenticated remote attacker to read full facility configurations and write unauthorized data to the sensor database. This issue has been fixed in version 2.4.18.029
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceICU Scandinavia Boomerang device receiver endpoints lack authentication controls, allowing any remote attacker to access them without credentials. This enables unauthenticated reading of complete facility configurations and unauthorized writes to the sensor database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Boomerang device receiver modelLocate the physical device or check network inventory for ICU Scandinavia Boomerang receiver hardware. Look for device labeling, DHCP lease records, or network scan results showing the device manufacturer and model.Affected if The device is an ICU Scandinavia Boomerang receiver and the version is below 2.4.18.029
-
Determine the installed firmware versionAccess the device web interface or check the device configuration file or system information for the firmware/build number. Compare against version 2.4.18.029.Affected if The installed version is older than 2.4.18.029 or the version cannot be determined
-
Verify authentication is required on device endpointsAttempt to access common device API endpoints (such as /api/config, /api/sensors, or similar facility configuration URLs) without providing credentials. Check if the device returns configuration data or allows sensor database writes without authentication.Affected if Unauthenticated requests to device endpoints return facility configuration data or allow writes to the sensor database
-
Check network exposure of device management interfaceReview firewall rules, network ACLs, or VLAN configurations to determine if the Boomerang device receiver management ports are accessible from untrusted or external networks. Use network scanning tools to confirm if the device is reachable from non-trusted IP addresses.Affected if The device receiver endpoints are reachable from untrusted networks without network segmentation or firewall restrictions
A user is affected if they have an ICU Scandinavia Boomerang device receiver running firmware below version 2.4.18.029 with endpoints accessible from untrusted networks and no authentication required for configuration reads or sensor writes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 2.4.18.029 which includes authentication fixes. If immediate upgrade is not possible, implement network segmentation or firewall rules to restrict access to device receiver endpoints to trusted sources only.
2.4.18.029
- 1. Identify all deployed instances of ICU Scandinavia Boomerang in your environment
- 2. Check the current version of each Boomerang instance
- 3. For any instance running a version lower than 2.4.18.029, obtain the version 2.4.18.029 update from the vendor
- 4. Apply the upgrade to each affected instance following the vendor's upgrade procedures
- 5. Verify the upgrade was successful by checking the version number
- 6. Confirm that the device receiver endpoints now require authentication
- 7. Test that unauthenticated requests to device receiver endpoints are rejected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46459 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46459 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data