dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2026-46458

HIGH · 7.1 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges Zero-click 5 weeks old

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 · unedited
ICU Scandinavia Boomerang is vulnerable to an information disclosure flaw where sensitive credential files are exposed via static HTTP. This allows an unauthenticated remote attacker to retrieve plaintext service account and SMTP credentials by requesting specific XML files from the webroot. 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 confidence

ICU Scandinavia Boomerang contains an information disclosure vulnerability where sensitive XML credential files (containing plaintext service account and SMTP credentials) are accessible via static HTTP requests to the webroot. An unauthenticated remote attacker can retrieve these credentials by directly requesting the XML files.

MitigationUpgrade to version 2.4.18.029 or later to remediate the vulnerability. If immediate patching is not possible, restrict external access to the webroot and remove any XML credential files from publicly accessible directories.

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:H/VI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Boomerang is accessible via HTTP
    Attempt to access the application's web interface using a browser or curl to the known IP/hostname on ports 80/443. Look for Boomerang-specific content or error messages.
    Affected if The Boomerang web interface is reachable from your network without authentication.
  2. Identify the installed Boomerang version
    Check the application's login page, about page, or HTTP headers for a version string. Compare the version number to the fixed version 2.4.18.029.
    Affected if The installed version is lower than 2.4.18.029.
  3. Enumerate XML files in the webroot
    Use a directory enumeration tool or manually guess common XML file names such as credentials.xml, config.xml, settings.xml, smtp.xml, or account.xml in the webroot directory accessible via HTTP.
    Affected if Any XML files containing credential data are present in the webroot.
  4. Verify XML credential files are accessible without authentication
    Directly request suspected XML credential files via HTTP GET (for example: curl http://target/credentials.xml). Check if the response contains plaintext usernames, passwords, or SMTP credentials.
    Affected if XML files containing plaintext credentials are retrievable without authentication.

A user is affected if the Boomerang application is accessible via HTTP and XML credential files containing plaintext credentials can be retrieved without any authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.4.18.029 or later to remediate the vulnerability. If immediate patching is not possible, restrict external access to the webroot and remove any XML credential files from publicly accessible directories.

Recommended fix High confidence

ICU Scandinavia Boomerang version 2.4.18.029 or later

  1. 1. Identify the current version of ICU Scandinavia Boomerang installed on the system
  2. 2. Create a complete backup of the current configuration, including all XML credential files and system settings
  3. 3. Download version 2.4.18.029 or a later stable release from the official ICU Scandinavia vendor
  4. 4. Stop the Boomerang service before applying the upgrade
  5. 5. Install the new version following the vendor's documented upgrade procedure
  6. 6. Restore the configuration from backup after upgrade, ensuring new security settings are applied
  7. 7. Restart the Boomerang service
  8. 8. Verify the upgrade was successful by checking the application version
Caveat Review vendor release notes for version 2.4.18.029 to check for any breaking changes or deprecated features; test in a non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46458 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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