dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-45291

HIGH · 7.5 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Cloudburst Network provides network components used within Cloudburst projects. A vulnerability in versions prior to `1.0.0.CR3-20260418.124334-32` impacts publicly accessible software depending on the affected versions of Network and allows an attacker to exploit a bug in Network to close the parent netty channel, rendering it inoperable. All consumers of the library should upgrade to at least version `1.0.0.CR3-20260418.124334-32`. There are no known workarounds beyond updating the library.

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 · moderate confidence

A vulnerability in Cloudburst Network library versions prior to 1.0.0.CR3-20260418.124334-32 allows an attacker to exploit a bug that enables closing the parent Netty channel, rendering it inoperable. This constitutes a denial-of-service condition affecting publicly accessible software that depends on the affected versions of the Network library.

MitigationUpgrade to version 1.0.0.CR3-20260418.124334-32 or later. No workarounds are available; immediate library update is required for all consumers.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Locate Cloudburst Network library in your project
    Search your project dependencies (Maven pom.xml, Gradle build.gradle, or equivalent) for a dependency named 'cloudburst-network', 'org.wildfly.security.cloudburst-network', or similar Cloudburst Network library entries.
    Affected if The library is present in your dependencies and the version is below 1.0.0.CR3-20260418.124334-32.
  2. Identify the exact version of Cloudburst Network library
    Run a dependency tree command (mvn dependency:tree for Maven or gradle dependencies for Gradle) and locate the cloudburst-network library version.
    Affected if The reported version is prior to 1.0.0.CR3-20260418.124334-32.
  3. Verify the library version from compiled artifacts
    If using a JAR file, inspect the MANIFEST.MF or check the library JAR filename directly for version information. The JAR may be named similarly to cloudburst-network-<version>.jar.
    Affected if The version string extracted is less than 1.0.0.CR3-20260418.124334-32 when compared lexicographically or numerically.
  4. Determine if the application is publicly accessible
    Review your network configuration and firewall settings to confirm whether the application using the Cloudburst Network library is exposed to untrusted network access or the public internet.
    Affected if The application using the affected library version is reachable from public networks without authentication barriers.

You are affected if your project depends on a version of Cloudburst Network library earlier than 1.0.0.CR3-20260418.124334-32 and that library is used by a publicly accessible application component.

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 1.0.0.CR3-20260418.124334-32 or later. No workarounds are available; immediate library update is required for all consumers.

Recommended fix Moderate confidence

1.0.0.CR3-20260418.124334-32

  1. 1. Identify all applications and services that depend on the Cloudburst Network library.
  2. 2. Check the current version of Cloudburst Network in each affected project (typically found in build files like pom.xml, package.json, or dependency management files).
  3. 3. If the current version is earlier than 1.0.0.CR3-20260418.124334-32, update the dependency to version 1.0.0.CR3-20260418.124334-32 or later.
  4. 4. Rebuild and redeploy all affected applications.
  5. 5. Verify that the public-facing services are functioning correctly after the update.
Caveat Review release notes for the new version to check for any API or behavioral changes that may affect your application

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45291 — 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-45291 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