CVE-2026-0714 Vulnerability Analysis & Exploit Details

CVE-2026-0714
Vulnerability Scoring

6.8
/10
High Risk

If left unpatched, CVE-2026-0714 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Physical
    Physical access is required to exploit this vulnerability.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-0714 Details

Status: Analyzed

Last updated: 🕠 18 Feb 2026, 17:55 UTC
Originally published on: 🕔 05 Feb 2026, 17:16 UTC

Time between publication and last update: 13 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2026-0714 Vulnerability Summary

CVE-2026-0714: A physical attack vulnerability exists in certain Moxa industrial computers using TPM-backed LUKS full-disk encryption on Moxa Industrial Linux 3, where the discrete TPM is connected to the CPU via an SPI bus. Exploitation requires invasive physical access, including opening the device and attaching external equipment to the SPI bus to capture TPM communications. If successful, the captured data may allow offline decryption of eMMC contents. This attack cannot be performed through brief or opportunistic physical access and requires extended physical access, possession of the device, appropriate equipment, and sufficient time for signal capture and analysis. Remote exploitation is not possible.

Assessing the Risk of CVE-2026-0714

Access Complexity Graph

The exploitability of CVE-2026-0714 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-0714

With low attack complexity and no required privileges, CVE-2026-0714 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-0714, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-0714, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-0714 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-0714 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-0714 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-0714 References

External References

CWE Common Weakness Enumeration

CWE-319

CAPEC Common Attack Pattern Enumeration and Classification

  • Session Sidejacking CAPEC-102 Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.
  • Interception CAPEC-117 An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information (e.g., targeting data leaks), the adversary must actively position themself so as to observe explicit data channels (e.g. network traffic) and read the content. However, this attack differs from a Adversary-In-the-Middle (CAPEC-94) attack, as the adversary does not alter the content of the communications nor forward data to the intended recipient.
  • Harvesting Information via API Event Monitoring CAPEC-383 An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a "virtual sale" of rare items. As other users enter the event, the attacker records via AiTM (CAPEC-94) proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.
  • Signature Spoofing by Mixing Signed and Unsigned Content CAPEC-477 An attacker exploits the underlying complexity of a data structure that allows for both signed and unsigned content, to cause unsigned data to be processed as though it were signed data.
  • Sniff Application Code CAPEC-65 An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.

Vulnerable Configurations

  • cpe:2.3:o:moxa:uc-1222a_firmware:1.4:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-1222a_firmware:1.4:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-1222a:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-1222a:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-2222a-t-us_firmware:1.4:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-2222a-t-us_firmware:1.4:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-2222a-t-us:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-2222a-t-us:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-2222a-t_firmware:1.4:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-2222a-t_firmware:1.4:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-2222a-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-2222a-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-2222a-t-ap_firmware:1.4:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-2222a-t-ap_firmware:1.4:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-2222a-t-ap:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-2222a-t-ap:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-2222a-t-eu_firmware:1.4:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-2222a-t-eu_firmware:1.4:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-2222a-t-eu:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-2222a-t-eu:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-3434a-t-lte-wifi_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-3434a-t-lte-wifi_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-3434a-t-lte-wifi:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-3434a-t-lte-wifi:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-3424a-t-lte_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-3424a-t-lte_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-3424a-t-lte:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-3424a-t-lte:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-3420a-t-lte_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-3420a-t-lte_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-3420a-t-lte:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-3420a-t-lte:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-3430a-t-lte-wifi_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-3430a-t-lte-wifi_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-3430a-t-lte-wifi:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-3430a-t-lte-wifi:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-4450a-t-5g_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-4450a-t-5g_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-4450a-t-5g:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-4450a-t-5g:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-4434a-i-t_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-4434a-i-t_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-4434a-i-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-4434a-i-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-4410a-t_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-4410a-t_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-4410a-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-4410a-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-4454a-t-5g_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-4454a-t-5g_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-4454a-t-5g:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-4454a-t-5g:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-4414a-i-t_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-4414a-i-t_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-4414a-i-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-4414a-i-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-4430a-t_firmware:1.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-4430a-t_firmware:1.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-4430a-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-4430a-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8210-t-lx-s_firmware:1.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8210-t-lx-s_firmware:1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8210-t-lx-s_firmware:1.5:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8210-t-lx-s_firmware:1.5:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-8210-t-lx-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-8210-t-lx-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-eu-s_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-eu-s_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-eu-s_firmware:1.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-eu-s_firmware:1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-eu-s_firmware:1.5:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-eu-s_firmware:1.5:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-8220-t-lx-eu-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-8220-t-lx-eu-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-ap-s_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-ap-s_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-ap-s_firmware:1.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-ap-s_firmware:1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-ap-s_firmware:1.5:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-ap-s_firmware:1.5:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-8220-t-lx-ap-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-8220-t-lx-ap-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-us-s_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-us-s_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-us-s_firmware:1.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-us-s_firmware:1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx-us-s_firmware:1.5:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx-us-s_firmware:1.5:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-8220-t-lx-us-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-8220-t-lx-us-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx_firmware:1.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx_firmware:1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:uc-8220-t-lx_firmware:1.5:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:uc-8220-t-lx_firmware:1.5:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:uc-8220-t-lx:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:uc-8220-t-lx:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v1202-ct-t_firmware:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v1202-ct-t_firmware:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v1202-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v1202-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v1222-ct-t_firmware:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v1222-ct-t_firmware:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v1222-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v1222-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v1222-w-ct-t_firmware:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v1222-w-ct-t_firmware:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v1222-w-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v1222-w-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-kl7-ct-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-kl7-ct-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-kl7-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-kl7-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-kl7-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-kl7-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-kl7-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-kl7-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-wl7-ct-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-wl7-ct-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-wl7-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-wl7-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-wl5-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-wl5-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-wl5-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-wl5-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-kl1-ct-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-kl1-ct-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-kl1-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-kl1-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-wl3-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-wl3-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-wl3-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-wl3-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-wl1-ct-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-wl1-ct-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-wl1-ct-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-wl1-ct-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-kl3-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-kl3-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-kl3-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-kl3-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-wl1-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-wl1-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-wl1-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-wl1-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-kl1-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-kl1-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-kl1-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-kl1-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-wl7-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-wl7-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-wl7-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-wl7-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:v2406c-kl5-t_firmware:1.2:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:v2406c-kl5-t_firmware:1.2:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:v2406c-kl5-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:v2406c-kl5-t:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-0714: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-3288 – A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/rewrite-target` Ingress annotation can be used to inject co...
  • CVE-2026-31816 – Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.4 and earlier, the Budibase server's authorized()...
  • CVE-2026-30240 – Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.5 and earlier, a path traversal vulnerability in ...
  • CVE-2026-25960 – vLLM is an inference and serving engine for large language models (LLMs). The SSRF protection fix for CVE-2026-24779 add in 0.15.1 can be bypassed ...
  • CVE-2026-25737 – Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.24.0 and earlier, an arbitrary file upload vulnerabi...