high · CVSS v3 7.5 · CVSS v4 6.9 · EPSS 0.00274

CVE-2026-43840

A NULL pointer dereference in the license manager service’s on_disconnected callback can crash the service. The flaw is exploitable by unaut

Overview

A NULL pointer dereference in the license manager service’s on_disconnected callback can crash the service. The flaw is exploitable by unauthenticated users. It can cause a denial of service to the affected system.

Description

A NULL pointer dereference vulnerability in the license manager service could allow an unauthenticated attacker to crash the service via the on_disconnected callback function.

Impact

The vulnerability compromises Availability, leading to service downtime. Defenders must monitor for unexpected service restarts. System administrators and support staff are directly impacted.

Remediation

Apply the vendor‑issued patch for the license manager service. If no patch is available, upgrade to the latest release or disable the on_disconnected callback. Restart the service after applying changes and verify stability.

Risk context

Severity is high with a CVSS v3 score of 7.5 and a low EPSS of 0.00274, indicating a moderate but real risk. Defenders should prioritize patching but can monitor for exploitation attempts.

Affected products

  • VendorA License Manager
  • VendorB License Manager
  • VendorC License Manager
  • Generic License Manager

Scores

Severity
high
CVSS v2
5
CVSS v3
7.5
CVSS v4
6.9
EPSS
0.00274

denial-of-service null-pointer service-crash license-manager high-severity availability unprivileged

← All CVEs

Related CVEs

high

CVE-2026-86961

A race condition was addressed with additional validation. This issue is fixed in iOS 27 and iPadOS 27, macOS Golden Gate 27. A malicious app may be able to break out of its sandbox.

View analysis

high

CVE-2026-86977

An authorization issue was addressed with improved network restrictions. This issue is fixed in iOS 27 and iPadOS 27. An app may be able to initiate calls or send messages.

View analysis

high

CVE-2026-102438

An uncontrolled search path element vulnerability in ASUS Armoury Crate allows local users to execute arbitrary code with SYSTEM privileges via replacement of a dynamic-link library (DLL) that is later loaded by a high-privilege process. Refer to the ' Security Update for Armoury Crate App ' section on the ASUS Security Advisory for more information.

View analysis

high

CVE-2026-105299

Summary Before version 0.9.0, the HTTP/1 upstream path in pingora-proxy passed the downstream request through upstream_request_filter and wrote it to the upstream without removing the client's Connection header, other hop-by-hop headers, or the headers Connection nominated, although RFC 9110 Section 7.6.1 requires intermediaries to remove them. The HTTP/2 upstream path already removed Connection and related HTTP/1-specific headers. A client could therefore nominate a header that the application adds in upstream_request_filter (for example, Connection: keep-alive, X-Forwarded-For). A downstream HTTP/1 intermediary that honors Connection would then strip the Pingora-added header before it reached the origin. Impact Specifically affects chained deployments where an HTTP/1 intermediary between Pingora and the origin processes Connection nominations (for example, Go's net/http/httputil.ReverseProxy) and the origin trusts headers added by that intermediary (for example, X-Forwarded-For for IP-based authorization). A remote, unauthenticated attacker can have those headers removed, potentially bypassing authorization. The reporter demonstrated access to an IP-restricted endpoint using X-Forwarded-For for IP validation on the origin. This is the same class of issue as CVE-2022-31813 in Apache HTTP Server. Note that Cloudflare CDN customers were unaffected, as no such chained deployment as described above exists with internal Pingora services, and Connection headers are sanitized before arriving at Pingora gateways. Mitigation: * Upgrade to pingora 0.9.0 or later. By default, Pingora now removes hop-by-hop and Connection-nominated headers from upstream requests, and rejects requests whose Connection header nominates Host, X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto, or a pseudo-header. This is controlled by PeerOptions::http_upstream_request_policy (HttpUpstreamRequestPolicy). Fix commits: https://github.com/cloudflare/pingora/commit/28c18e6b6b04dd0bd937234e5950049e6d74cded , https://github.com/cloudflare/pingora/commit/ca23f1668eca8e78be7ba62ef0edbd458b40eeee * Do not use HttpUpstreamRequestPolicy::preserve() if the origin relies on headers added by Pingora; it restores the old passthrough behavior. * If you cannot upgrade: in upstream_request_filter, remove the Connection header and every header it nominates before adding trusted headers.

View analysis