dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-11044

MEDIUM · 6.8 CVSS v3.1 Published 2026-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
An Allocation of Resources Without Limits or Throttling vulnerability in the ANSL-Server component of B&R Automation Runtime versions prior to 6.5 and prior to R4.93 could be exploited by an unauthenti-cated attacker on the network to win a race condition, resulting in permanent denial-of-service (DoS) conditions on affected devices.

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

A race condition vulnerability exists in the ANSL-Server (Automation Networks Services Layer) component of B&R Automation Runtime. An unauthenticated network attacker can exploit this resource allocation flaw to win a race condition, causing permanent denial-of-service that likely requires physical intervention to recover.

MitigationUpgrade B&R Automation Runtime to version 6.5 or later, or R4.93 or later. Apply network segmentation and firewall rules to restrict unauthorized network access to the ANSL-Server.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 B&R Automation Runtime installation
    Locate B&R Automation Runtime software on the system. Check installed programs or look for B&R automation software directories. Confirm the product name matches 'B&R Automation Runtime'.
    Affected if B&R Automation Runtime is installed on the system
  2. Determine installed version of Automation Runtime
    Access the system control panel, B&R-specific software management tool, or check program version information. Note the exact version number installed.
    Affected if The installed version is lower than 6.5 or lower than R4.93 (or version cannot be determined to be at or above these releases)
  3. Verify ANSL-Server component status
    Check if the ANSL-Server (Automation Networks Services Layer) is running or enabled on the system. This may be visible in services, running processes, or B&R configuration tools.
    Affected if ANSL-Server is enabled and running on the system
  4. Assess network exposure of ANSL-Server
    Review network configuration, firewall rules, and port bindings to determine if the ANSL-Server component is accessible from the network. Check for open ports typically used by ANSL or industrial automation protocols.
    Affected if ANSL-Server is listening on network-accessible ports and can be reached by unauthenticated network attackers

A user is affected if B&R Automation Runtime is installed with a version prior to 6.5 or prior to R4.93, the ANSL-Server component is enabled, and the service is exposed to unauthenticated network access.

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 B&R Automation Runtime to version 6.5 or later, or R4.93 or later. Apply network segmentation and firewall rules to restrict unauthorized network access to the ANSL-Server.

Recommended fix High confidence

B&R Automation Runtime version 6.5 or later, or version R4.93 or later

  1. 1. Identify the current B&R Automation Runtime version installed on the affected device.
  2. 2. If running a version prior to 6.5, plan for upgrade to version 6.5 or later.
  3. 3. If running a version prior to R4.93 (but after 6.5), plan for upgrade to version R4.93 or later.
  4. 4. Contact B&R Automation technical support or use official distribution channels to obtain the appropriate fixed version upgrade package.
  5. 5. Schedule a maintenance window as the upgrade may require device downtime.
  6. 6. Before applying the upgrade, backup all critical configurations and programs.
  7. 7. Apply the upgrade following B&R Automation's official documentation for your specific hardware model.
  8. 8. After upgrade, verify the ANSL-Server component is functioning correctly and the device is operational.
Caveat Review B&R Automation release notes for version 6.5 or R4.93 for any compatibility considerations or migration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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