dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2025-65082

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-05
Fix available
A fix is available. Upgrade to 2.4.66 or later.
See remediation →
74/100
Remediation priority · Elevated
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
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.

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

Apache HTTP Server allows environment variables to be set via configuration directives (SetEnv, PassEnv) which can unexpectedly override server-calculated CGI environment variables. This improper variable supersession could allow injection of escape, meta, or control sequences into CGI program environments, potentially affecting application behavior or security.

MitigationUpgrade Apache HTTP Server to version 2.4.66 or later. After upgrading, review and test all CGI applications to ensure expected environment variables are properly set and not being overridden by configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:>= 2.4.0, < 2.4.66

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

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

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. Check installed Apache version
    Run 'httpd -v' or 'apache2 -v' to get the server version number
    Affected if Version is 2.4.0 or higher but lower than 2.4.66
  2. Verify CGI module is enabled
    Run 'httpd -M' or 'apache2ctl -M' and look for 'cgi_module' in the loaded modules list, or check config files for 'LoadModule cgi_module'
    Affected if CGI module (mod_cgi) is loaded and enabled
  3. Check for SetEnv directives in configuration
    Search all Apache configuration files (httpd.conf, include files, vhost configs) for 'SetEnv' directives that set environment variables
    Affected if SetEnv directives are present that could override CGI environment variables
  4. Check for PassEnv directives in configuration
    Search all Apache configuration files for 'PassEnv' directives that pass environment variables from the shell to CGI scripts
    Affected if PassEnv directives are present that could override server-calculated CGI variables
  5. Identify CGI script configurations
    Look for 'ScriptAlias', 'Options +ExecCGI', 'AddHandler cgi-script', or similar CGI handler configurations in the Apache config files
    Affected if CGI scripts are configured and the above SetEnv/PassEnv conditions are met

User is affected if running Apache 2.4.0-2.4.65 with CGI module enabled and SetEnv or PassEnv directives configured in a way that could override server-calculated CGI environment variables.

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
Upgrade available Upgrade to 2.4.66 or later
Fixed in 2.4.66
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.66 or later. After upgrading, review and test all CGI applications to ensure expected environment variables are properly set and not being overridden by configuration.

Recommended fix High confidence

Apache HTTP Server 2.4.66

  1. 1. Check current Apache HTTP Server version using: httpd -v or apache2 -v
  2. 2. Download Apache HTTP Server 2.4.66 from the official Apache website (httpd.apache.org)
  3. 3. Back up current Apache configuration files (httpd.conf, any included config files)
  4. 4. Install Apache HTTP Server 2.4.66 using standard installation procedures for your operating system
  5. 5. Restore or merge your existing Apache configuration files to the new installation
  6. 6. Restart the Apache service: systemctl restart httpd (or apache2ctl restart)
  7. 7. Verify the upgrade was successful by checking the version: httpd -v
Caveat Review Apache 2.4.66 release notes for any configuration or module compatibility changes before upgrading

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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