CVE-2026-1642 Vulnerability Analysis & Exploit Details

CVE-2026-1642
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2026-1642 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • 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-1642 Details

Status: Analyzed

Last updated: 🕤 13 Feb 2026, 21:35 UTC
Originally published on: 🕒 04 Feb 2026, 15:16 UTC

Time between publication and last update: 9 days

CVSS Release: version 3

CVSS3 Source

f5sirt@f5.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-1642 Vulnerability Summary

CVE-2026-1642: A vulnerability exists in NGINX OSS and NGINX Plus when configured to proxy to upstream Transport Layer Security (TLS) servers. An attacker with a man-in-the-middle (MITM) position on the upstream server side—along with conditions beyond the attacker's control—may be able to inject plain text data into the response from an upstream proxied server.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Assessing the Risk of CVE-2026-1642

Access Complexity Graph

The exploitability of CVE-2026-1642 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-1642

CVE-2026-1642 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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-1642, 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-1642, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-1642 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2026-1642 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-1642 does not impact system availability.

CVE-2026-1642 References

External References

CWE Common Weakness Enumeration

CWE-345

CAPEC Common Attack Pattern Enumeration and Classification

  • JSON Hijacking (aka JavaScript Hijacking) CAPEC-111 An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website.
  • Cache Poisoning CAPEC-141 An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.
  • DNS Cache Poisoning CAPEC-142 A domain name server translates a domain name (such as www.example.com) into an IP address that Internet hosts use to contact Internet resources. An adversary modifies a public DNS cache to cause certain names to resolve to incorrect addresses that the adversary specifies. The result is that client applications that rely upon the targeted cache for domain name resolution will be directed not to the actual address of the specified domain name but to some other address. Adversaries can use this to herd clients to sites that install malware on the victim's computer or to masquerade as part of a Pharming attack.
  • Content Spoofing CAPEC-148 An adversary modifies content to make it contain something other than what the original content producer intended while keeping the apparent source of the content unchanged. The term content spoofing is most often used to describe modification of web pages hosted by a target to display the adversary's content instead of the owner's content. However, any content can be spoofed, including the content of email messages, file transfers, or the content of other network communication protocols. Content can be modified at the source (e.g. modifying the source file for a web page) or in transit (e.g. intercepting and modifying a message between the sender and recipient). Usually, the adversary will attempt to hide the fact that the content has been modified, but in some cases, such as with web site defacement, this is not necessary. Content Spoofing can lead to malware exposure, financial fraud (if the content governs financial transactions), privacy violations, and other unwanted outcomes.
  • Spoofing of UDDI/ebXML Messages CAPEC-218 An attacker spoofs a UDDI, ebXML, or similar message in order to impersonate a service provider in an e-business transaction. UDDI, ebXML, and similar standards are used to identify businesses in e-business transactions. Among other things, they identify a particular participant, WSDL information for SOAP transactions, and supported communication protocols, including security protocols. By spoofing one of these messages an attacker could impersonate a legitimate business in a transaction or could manipulate the protocols used between a client and business. This could result in disclosure of sensitive information, loss of message integrity, or even financial fraud.
  • Application API Message Manipulation via Man-in-the-Middle CAPEC-384 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to perform adversary-in-the-middle (CAPEC-94) communications between the web browser and the remote system. Despite the use of AiTH software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Adversary-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.
  • Transaction or Event Tampering via Application API Manipulation CAPEC-385 An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.
  • Application API Navigation Remapping CAPEC-386 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.
  • Navigation Remapping To Propagate Malicious Content CAPEC-387 An adversary manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic.
  • Application API Button Hijacking CAPEC-388 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.
  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.
  • Browser in the Middle (BiTM) CAPEC-701 An adversary exploits the inherent functionalities of a web browser, in order to establish an unnoticed remote desktop connection in the victim's browser to the adversary's system. The adversary must deploy a web client with a remote desktop session that the victim can access.

Vulnerable Configurations

  • cpe:2.3:a:f5:nginx_gateway_fabric:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_gateway_fabric:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_gateway_fabric:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_gateway_fabric:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_gateway_fabric:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_gateway_fabric:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_gateway_fabric:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_gateway_fabric:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:3.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:3.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:5.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:5.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:5.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:5.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_ingress_controller:5.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_ingress_controller:5.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.17.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.17.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.17.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.17.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.17.3:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.17.3:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.17.4:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.17.4:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.19.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.19.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_instance_manager:2.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_instance_manager:2.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.5.13:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.5.13:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.25.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.25.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.25.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.25.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.25.3:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.25.3:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.25.4:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.25.4:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.26.1:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.26.1:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.26.2:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.26.2:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.27.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.27.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_open_source:1.29.0:*:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_open_source:1.29.0:*:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r33:-:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r33:-:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r34:-:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r34:-:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r32:-:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r32:-:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r32:p1:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r32:p1:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r32:p2:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r32:p2:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r32:p3:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r32:p3:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r33:p1:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r33:p1:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r33:p2:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r33:p2:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r33:p3:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r33:p3:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r34:p1:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r34:p1:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r34:p2:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r34:p2:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r35:-:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r35:-:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r36:-:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r36:-:*:*:*:*:*:*
  • cpe:2.3:a:f5:nginx_plus:r36:p1:*:*:*:*:*:*
    cpe:2.3:a:f5:nginx_plus:r36:p1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-1642: 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...