Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed tsmemcache interface
-
ExploitSend unauthenticated cache command
-
ExecutionRead, overwrite, or delete cached objects
-
ImpactPoison proxy cache served to all clients
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target Apache Traffic Server deployment has loaded and enabled the experimental tsmemcache plugin, which exposes a memcache-style network interface to the shared proxy cache; this plugin is explicitly 'experimental' and is NOT enabled in a default ATS installation - this is the single most important limiting factor and is reflected by AT:P in the CVSS 4.0 vector. Once the plugin's interface is network-reachable, no authentication, privileges, or user interaction are required (PR:N/UI:N), so any attacker who can connect to the exposed port can read, write, and delete cache entries. Limiting factors for defenders: the non-default experimental plugin must be in use, and the interface must be reachable from the attacker's network position; affected version must be in the ranges 8.0.0-8.1.11, 9.0.0-9.2.15, 10.0.0-10.1.4, or 10.2.0. |
| Impact | Signals mostly align toward high severity but with one important mitigating condition. The CVSS 4.0 base score of 9.4 reflects a network vector (AV:N), low attack complexity (AC:L), no privileges (PR:N), and no user interaction (UI:N), with high confidentiality, integrity, and availability impact (VC:H/VI:H/VA:H) - consistent with CWE-306 (Missing Authentication) allowing unauthenticated read, write, and delete of the shared proxy cache. The critical nuance is AT:P (Attack Requirements: Present), which signals that exploitation depends on a specific deployment condition: the plugin involved is explicitly described as 'experimental' (tsmemcache) and is not part of a default Apache Traffic Server configuration. No EPSS score was provided, this CVE is NOT listed in CISA KEV, and no public exploit code is referenced, so there is no public exploit identified at time of analysis. Net assessment: this is a genuinely serious, low-complexity unauthenticated flaw for the subset of operators who have explicitly enabled the experimental tsmemcache plugin, but the real-world attack surface is narrowed sharply by that non-default dependency - treat as high priority for ATS operators who use tsmemcache, and routine patch management otherwise. Missing data to note: EPSS probability is absent, and the odd input CVSS 4.0 subsequent-system metrics (SC:N/SI:N/SA:H) are internally inconsistent (availability impact on a subsequent system with no other subsequent impact) and should be verified against the Apache advisory. |
| Exploit ScenarioDerived | An Apache Traffic Server operator has enabled the experimental tsmemcache plugin, exposing a memcache-style interface on the network with no authentication. A remote attacker who can reach that port sends unauthenticated commands to read sensitive cached responses, overwrite entries to poison the cache served to all downstream users, or delete entries to disrupt service. No public exploit code is identified at time of analysis, but the attack requires no credentials or user interaction once the plugin is reachable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 21, 2026
Unauthenticated network access to the shared proxy cache is possible in Apache Traffic Server deployments that load and enable the experimental tsmemcache plugin, allowing remote attackers to read, modify, and delete cached objects without credentials. Affected releases span 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0; the exposure is gated by the plugin being explicitly enabled and its memcache-style interface being network-reachable, since it is not active in a default installation. No public exploit code or confirmed active exploitation was identified at time of analysis, though the CVSS 4.0 base score of 9.4 and the unauthenticated nature of the interface once exposed make this a high-priority fix for anyone running the plugin.
Earlier versions of this analysis (1)
Unauthenticated network attackers can read, write, and delete entries in the shared proxy cache of Apache Traffic Server when the experimental tsmemcache plugin is explicitly loaded and network-reachable, affecting versions 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0. The plugin is not enabled by default, so exposure requires a non-standard configuration that exposes the memcache-style interface. No public exploit code has been identified at the time of analysis, and exploitation requires the plugin to be active and accessible over the network.
RemediationAI
Vendor-released patch: upgrade to Apache Traffic Server 9.2.16, 10.1.5, or 10.2.1 as documented in the Apache advisory at https://lists.apache.org/thread/r95dq29ywcd1f4x30snxlqmb12z4s4kc. Organizations on 8.x must move to a supported fixed branch (9.2.16 or later, or 10.2.1) since no 8.x fix is listed. If upgrading cannot be completed immediately, the most effective compensating control is to disable and unload the experimental tsmemcache plugin (remove its configuration entry and restart ATS) - the trade-off is loss of the memcache-compatible cache-manipulation functionality the plugin provides, which is acceptable given the plugin's experimental status. Where the plugin must remain active, restrict its listening port to trusted management networks with a stateful firewall or network ACL and bind the plugin interface to a loopback or internal-only address; the trade-off is that any legitimate remote memcache clients must be relocated or proxied through an authorized host, and network segmentation failures silently reintroduce full unauthenticated cache access. Monitor ATS logs for unexpected connections to the plugin's port and for anomalous cache deletions or injected objects as a detection measure while remediation is in progress.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Traffic Server is a caching proxy and origin server; the tsmemcache plugin is an experimental component that layers a memcache-style protocol interface over ATS's shared proxy cache so external clients can manipulate cache contents. The root cause is CWE-306 (Missing Authentication for Critical Function): the plugin exposes read, write, and delete operations on cache entries over the network with no authentication or authorization check whatsoever. From an implementation standpoint the protocol handler trusts any connecting peer, so object integrity and confidentiality of cached content depend entirely on network isolation rather than on any access control in the plugin itself. The CVSS 4.0 vector's AT:P (Attack Requirements: Present) accurately captures the key precondition - the experimental plugin must have been compiled in, loaded via configuration, and its listening interface made reachable - which is why the base metrics (AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and subsequent-system availability impact) combine with a deployment-specific prerequisite. The CPE entry confirms the affected package is the Apache Software Foundation's Apache Traffic Server distribution itself, meaning all downstream packages and appliances bundling these versions inherit the exposure if the plugin is enabled.
Know when Apache Traffic Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H
Unauthenticated network access with no interaction yields AV:N/AC:L/PR:N/UI:N and full C/I/A loss of the cache; the non-default experimental-plugin requirement is a deployment precondition not captured by 3.1 base metrics.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
4DescriptionCVE.org
Apache Traffic Server's experimental tsmemcache plugin allows unauthenticated network read, write, and deletion of the shared proxy cache.
This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0.
Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.
Executive ViewAI
Apache Traffic Server deployments that enable the experimental tsmemcache plugin are exposed to remote manipulation of cached objects, potentially affecting the confidentiality and integrity of proxied content. The exposure is limited to non-default configurations where the plugin is loaded and its memcache-style interface is network-reachable, so leadership should focus on confirming which systems meet those conditions and removing that attack surface while a vendor fix is pending. No public exploit identified at time of analysis, but the critical severity and cache-integrity risk justify urgent validation and containment.
No vendor-released patch identified at time of analysis; disable or unload the experimental tsmemcache plugin, block network reachability to its memcache-style interface, restrict proxy cache management to trusted networks, monitor for unauthorized cache object changes, and upgrade when a vendor fix becomes available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Apache Traffic Server
View allApache Traffic Server versions 8.0.1 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0 ship an exp
Remote denial of service in Apache Traffic Server (8.0.0-8.1.9, 9.0.0-9.2.14, 10.0.0-10.1.3) allows unauthenticated atta
Out-of-bounds write and integer overflow in Apache Traffic Server's MIME and HTTP header parsing lets remote attackers c
Request smuggling and policy bypass in Apache Traffic Server (branches 8.0.0-8.1.9, 9.0.0-9.2.14, and 10.0.0-10.1.3) ari
Response-framing desync in Apache Traffic Server (8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and
Request smuggling in Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0
Unauthenticated remote attackers can drive HTTP transactions to completion against Apache Traffic Server instances that
Denial of service in Apache Traffic Server 8.0.0-8.1.9, 9.0.0-9.2.14, and 10.0.0-10.1.3 lets remote unauthenticated atta
Apache Traffic Server 9.2.15, 10.1.4, and 10.2.0 can be driven into a denial-of-service condition through log amplificat
Out-of-bounds write and limit-bypass flaws in several experimental plugins shipped with Apache Traffic Server (8.0.0-8.1
Improper certificate generation in the Apache Traffic Server certifier plugin lets remote attackers dictate the contents
Memory corruption in Apache Traffic Server's remap configuration handling lets remote attackers trigger a use-after-free
EUVD-2026-107535
GHSA-98jq-8c4p-7mh6
NVD
CVE.org
EPSS
Exploit-DB