Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-45290

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-20260417.085727-30` impacts publicly accessible software depending on the affected versions of Network and allows an attacker to exploit a vulnerability in Network to stall the netty event loop, rendering it inoperable. All consumers of the library should upgrade to at least version `1.0.0.CR3-20260417.085727-30`. 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 allows remote attackers to stall the Netty event loop, causing denial of service. This affects publicly accessible software depending on affected versions of the Network component.

MitigationUpgrade Cloudburst Network to version 1.0.0.CR3-20260417.085727-30 or later. No workarounds are available; immediate patching is required.

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. Identify Cloudburst Network library usage
    Search project dependency files (pom.xml, build.gradle, requirements.txt) or compiled JARs for 'cloudburst-network' or 'cloudburst' artifacts
    Affected if The Cloudburst Network library is present as a dependency
  2. Determine installed library version
    Examine the resolved library version in your dependency management system, build output, or inspect the JAR file manifest/META-INF for version metadata
    Affected if The version is older than 1.0.0.CR3-20260417.085727-30 or cannot be determined to be that version or later
  3. Verify publicly accessible Network component
    Review network exposure settings, firewall rules, or service bindings to determine if the Network component listens on external interfaces (0.0.0.0 or public IP addresses)
    Affected if The Network component is bound to publicly reachable network interfaces
  4. Check Netty event loop configuration
    Inspect configuration files or code that initializes the Netty event loop group used by Cloudburst Network
    Affected if A custom event loop group is configured that may be vulnerable to stalling
  5. Confirm application type
    Review application architecture documentation or code to verify it uses the affected Network component for remote communications
    Affected if The application relies on Cloudburst Network for remote client connections

You are affected if your environment uses a version of Cloudburst Network library older than 1.0.0.CR3-20260417.085727-30 and the Network component is publicly accessible.

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 Cloudburst Network to version 1.0.0.CR3-20260417.085727-30 or later. No workarounds are available; immediate patching is required.

Recommended fix High confidence

1.0.0.CR3-20260417.085727-30 or later

  1. Locate the Cloudburst Network dependency in your project's dependency management file (e.g., pom.xml, build.gradle, requirements.txt)
  2. Update the Cloudburst Network library version to at least 1.0.0.CR3-20260417.085727-30
  3. Rebuild and redeploy your application to ensure the updated library is in use

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45290 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