VulnerabilityPublished 23 Jul 2025Updated 5 Nov 2025

CVE-2025-54090: Apache HTTP Server · Bug

Source GCVE Database

Compare

Authoritative record:CVE-2025-54090· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium · fixed in 2.4.65 : update affected systems when convenient.

Data as of 4 Nov 2026, 17:55 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	6.3

Patch: Available – fixed in 2.4.65

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-cjqj-vhhm-xq5x

What to do

AI-suggested

Users should upgrade Apache HTTP Server to version 2.4.65, which contains the official fix for this vulnerability. No other mitigation is necessary once the upgrade is applied.

Description

A bug in Apache HTTP Server version 2.4.64 causes all "RewriteCond expr ..." conditional tests to evaluate as true, potentially leading to unintended behavior in URL rewriting rules. The issue is fixed in version 2.4.65, and users are advised to upgrade to this version.

Impact

The vulnerability causes all conditional expressions in "RewriteCond expr ..." directives to evaluate as true, which may lead to unintended URL rewriting behavior. This can affect confidentiality, integrity, and availability to a limited extent, as indicated by the CVSS vector (C:L/I:L/A:L). No known exploits are reported in the wild.

Summary

CVE-2025-54090 describes a vulnerability in Apache HTTP Server 2.4.64 where the "RewriteCond expr ..." directive incorrectly evaluates all conditions as true. This flaw can cause rewrite rules to behave unexpectedly, potentially impacting the integrity of URL rewriting logic. The vulnerability has a CVSS 3.1 base score of 6.3, indicating a medium severity level. The issue is resolved in Apache HTTP Server version 2.4.65.

CWE-253Incorrect Check of Function Return Value (opens in a new tab)
Base weaknessLikelihood of exploit: Low
The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.
Architecture and Design · Language Selection
Use a language or compiler that uses exceptions and requires the catching of those exceptions.
Implementation
Properly check all functions which return a value.
Implementation
When designing any function make sure you return a value or throw an exception in case of an error.
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2026, 17:55 UTC

WeaknessesCWE-253

Technical details

References

Community reviews

Related threats