CVE-2025-65082 Vulnerability Analysis & Exploit Details

CVE-2025-65082
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2025-65082 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: 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-2025-65082 Details

Status: Analyzed

Last updated: 🕟 10 Dec 2025, 16:39 UTC
Originally published on: 🕚 05 Dec 2025, 11:15 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-65082 Vulnerability Summary

CVE-2025-65082: Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache HTTP Server through environment variables set via the Apache configuration unexpectedly superseding variables calculated by the server for CGI programs. This issue affects Apache HTTP Server from 2.4.0 through 2.4.65. Users are recommended to upgrade to version 2.4.66 which fixes the issue.

Assessing the Risk of CVE-2025-65082

Access Complexity Graph

The exploitability of CVE-2025-65082 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-2025-65082

With low attack complexity and no required privileges, CVE-2025-65082 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-2025-65082, 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-2025-65082, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-65082 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2025-65082 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2025-65082 does not impact system availability.

CVE-2025-65082 References

External References

CWE Common Weakness Enumeration

CWE-150

CAPEC Common Attack Pattern Enumeration and Classification

  • Email Injection CAPEC-134 An adversary manipulates the headers and content of an email message by injecting data via the use of delimiter characters native to the protocol.
  • Using Meta-characters in E-mail Headers to Inject Malicious Payloads CAPEC-41 This type of attack involves an attacker leveraging meta-characters in email headers to inject improper behavior into email programs. Email software has become increasingly sophisticated and feature-rich. In addition, email applications are ubiquitous and connected directly to the Web making them ideal targets to launch and propagate attacks. As the user demand for new functionality in email applications grows, they become more like browsers with complex rendering and plug in routines. As more email functionality is included and abstracted from the user, this creates opportunities for attackers. Virtually all email applications do not list email header information by default, however the email header contains valuable attacker vectors for the attacker to exploit particularly if the behavior of the email client application is known. Meta-characters are hidden from the user, but can contain scripts, enumerations, probes, and other attacks against the user's system.
  • Web Server Logs Tampering CAPEC-81 Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
  • Log Injection-Tampering-Forging CAPEC-93 This attack targets the log files of the target host. The attacker injects, manipulates or forges malicious log entries in the log file, allowing them to mislead a log audit, cover traces of attack, or perform other malicious actions. The target host is not properly controlling log access. As a result tainted data is resulting in the log files leading to a failure in accountability, non-repudiation and incident forensics capability.

Vulnerable Configurations

  • cpe:2.3:a:apache:http_server:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.9:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.10:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.10:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.11:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.12:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.12:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.13:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.13:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.14:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.14:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.15:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.15:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.16:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.16:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.17:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.17:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.18:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.18:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.19:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.19:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.20:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.20:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.21:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.21:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.22:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.22:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.23:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.23:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.24:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.24:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.25:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.25:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.26:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.26:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.27:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.27:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.28:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.28:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.29:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.29:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.30:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.30:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.31:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.31:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.32:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.32:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.33:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.33:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.34:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.34:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.35:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.35:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.36:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.36:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.37:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.37:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.38:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.38:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.39:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.39:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.40:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.40:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.41:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.41:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.42:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.42:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.43:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.43:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.44:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.44:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.45:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.45:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.46:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.46:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.47:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.47:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.48:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.48:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.50:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.50:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.52:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.52:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.53:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.53:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.54:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.54:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.55:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.55:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.56:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.56:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.57:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.57:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.58:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.58:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.59:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.59:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.60:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.60:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.61:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.61:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.62:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.62:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.63:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.63:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.64:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.64:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.65:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.65:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-65082: 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-2025-15165 – A vulnerability has been found in itsourcecode Online Cake Ordering System 1.0. The impacted element is an unknown function of the file /updatecust...
  • CVE-2025-15164 – A security flaw has been discovered in Tenda WH450 1.0.0.18. This affects an unknown part of the file /goform/SafeMacFilter. The manipulation of th...
  • CVE-2025-15163 – A vulnerability was identified in Tenda WH450 1.0.0.18. Affected by this issue is some unknown functionality of the file /goform/SafeEmailFilter. T...
  • CVE-2025-15067 – Unrestricted Upload of File with Dangerous Type vulnerability in Innorix Innorix WP allows Upload a Web Shell to a Web Server.This issue affects In...
  • CVE-2025-15066 – Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Missing Authorization vulnerability in Innorix WP allows Path Trave...