Apache
Monthly
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Directory traversal vulnerability in the fileserver upload/download functionality for blob messages in Apache ActiveMQ 5.x before 5.11.2 for Windows allows remote attackers to create JSP files in. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 86.0%.
GNU Bash through 4.3 bash43-026 does not properly parse function definitions in the values of environment variables, which allows remote attackers to execute arbitrary commands via a crafted. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 92.7%.
ParametersInterceptor in Apache Struts before 2.3.20 does not properly restrict access to the getClass method, which allows remote attackers to "manipulate" the ClassLoader and execute arbitrary code. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 91.4%.
The ParametersInterceptor in Apache Struts before 2.3.16.2 allows remote attackers to "manipulate" the ClassLoader via the class parameter, which is passed to the getClass method. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 93.1%.
Certain getText methods in the ActionSupport controller in Apache Roller before 5.0.2 allow remote attackers to execute arbitrary OGNL expressions via the first or second parameter, as demonstrated. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 87.0%.
Apache Struts 2.0.0 through 2.3.15 allows remote attackers to execute arbitrary OGNL expressions via a parameter with a crafted (1) action:, (2) redirect:, or (3) redirectAction: prefix. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2). Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, no authentication required. Public exploit code available and EPSS exploitation probability 87.6%.
Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2). Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 91.1%.
The DebuggingInterceptor component in Apache Struts before 2.3.1.1, when developer mode is used, allows remote attackers to execute arbitrary commands via unspecified vectors. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 92.6%.
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during certain exception handling for mismatched data types of properties, which. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Let me synthesize. CVE-2026-86465: Apache Airflow Akeyless provider secrets backend team-scope guard bypass via user-controlled key. Affected: apache-airflow-providers-akeyless before 0.3.1. Fix: 0.3.1. PR: https://github.com/apache/airflow/pull/72646. Similar class to Azure Key Vault, Yandex Lockbox, Amazon secrets backends CVEs. Multi-team deployments using Akeyless secrets backend; single-team not affected. Reachable from ordinary DAG code via Execution API Variables route accepting path-shaped key. DAG author scoped to one team can read secrets belonging to another team — info disclosure (cross-tenant secret access). CVSS: N/A provided. My assessed vector: PR:L (requires DAG author privileges / authenticated user), AV:N, AC:L, UI:N, S:C? Scope change — impacts another team's secrets, but scope change in CVSS terms means authorization scope. Cross-team boundary crossing could be S:C. Impact C:H, I:N, A:N. So CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. That's ~8.3? Let's compute: S:C base... Actually with S:C, PR:L: exploitability = 8.22*AV(0.85)*AC(0.77)*PR(0.68)*UI(0.85) = 8.22*0.85=6.987; *0.77=5.380; *0.68=3.658; *0.85=3.110. Impact: ISCBase = 1 - (1-C)(1-I)(1-A) = 1 - (1-0.56)(1)(1) = 0.56. Scope changed: Impact = 7.52*(ISC-0.029) - 3.25*(ISC-0.02)^15 = 7.52*(0.531) - 3.25*(0.54)^15 ≈ 3.993 - ~0 = 3.993. Base = roundup(min(1.08*(3.110+3.993),10)) = roundup(7.67) = 7.7. Hmm, 7.7 High. Maybe S:C is arguable. Alternatively S:U with C:H gives: Impact = 6.42*0.56 = 3.595; exploitability 3.110; base = roundup(min(1.08*6.705,10)) = roundup(7.24)=7.3. Either way ~7.3-7.7. Actually, "moderate" severity per Apache. Hmm. Apache's own severity is "moderate". But my assessment... I'll go with S:C? Let's think: the vulnerable component is the Akeyless backend; the impact is a different team's secrets. CVSS scope change refers to impact on components beyond the vulnerable component's security authority. The secrets backend... Hmm. This is a classic cross-tenant autho
Stale database-backed sessions in the Apache Airflow FAB provider (apache-airflow-providers-fab 3.2.0 before 3.9.0) allow an attacker who already holds a copy of a victim's session cookie to keep full access to that account even after the account password is changed, because the Admin user-edit PATCH endpoint never calls the session-invalidation helper. This is a second, independent route to the outcome partially addressed by CVE-2026-82311, so deployments that only applied that earlier fix remain exposed and must additionally upgrade to 3.9.0 or later. No public exploit code or active exploitation is identified from the available data; severity is rated moderate by the vendor.
Password changes made through the Apache Airflow FAB provider's Admin user-edit PATCH endpoint do not invalidate that user's existing database-backed sessions, so anyone already holding a copy of the victim's session cookie keeps full access to the account after the reset. The flaw affects apache-airflow-providers-fab 3.2.0 up to (but not including) 3.9.0 in deployments using the FAB auth manager with database-backed sessions, and it is a second, independent route to the outcome addressed by CVE-2026-82311 — applying that earlier fix alone does not remediate this endpoint. The advisory rates the issue moderate; no public exploit code, CISA KEV listing, or EPSS score was provided with the intelligence supplied.
The Apache Airflow Keycloak provider (apache-airflow-providers-keycloak before 0.10.0), when running on Airflow 3.3 or later, performs authorization using Keycloak access and refresh tokens read from separate, unsigned cookies while taking the user's identity from the signed Airflow session token, and never verifies that both describe the same subject. Any user
Path-name disclosure in Apache ZooKeeper 3.8.0 through 3.8.6 and 3.9.0 through 3.9.5 lets a connected client learn the names of ACL-restricted znodes by registering exists-watches on paths that do not yet exist and then reconnecting after those paths are created under restrictive ACLs. The reconnect replay handler DataTree.setWatches() delivers the watch notification with a null ACL, bypassing the ACL check that was added to WatchManager.triggerWatch() as the fix for CVE-2024-23944 (ZOOKEEPER-4799), making this an incomplete-fix bypass. Only the znode path string is exposed, not znode data, but because paths frequently embed usernames, login IDs, or tenant identifiers, Apache and the reporter rate it critical; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated topology submission in Apache Storm Nimbus 3.0.0 through 3.0.x allows any authenticated Storm user to read arbitrary files accessible to the Nimbus daemon by supplying a server-side path as the uploadedJarLocation argument to submitTopology or submitTopologyWithOpts, bypassing the intended beginFileUpload flow entirely. Nimbus copies the targeted file into a topology blob and automatically grants the submitter read access via blob ACLs, enabling retrieval of Kerberos keytabs, TLS private keys, and ZooKeeper credentials through standard blob download APIs. A proof of concept was submitted alongside disclosure; upgrade to Apache Storm 3.1.0 is the required remediation.
Open redirect in Apache Syncope's SRA (Secure Remote Access) component allows unauthenticated network attackers to redirect authenticated users to attacker-controlled URLs during CAS SSO login flows. The vulnerability arises because Syncope SRA unconditionally trusts client-supplied forwarded HTTP headers (e.g. X-Forwarded-Host, X-Forwarded-Proto) when constructing the target Apereo CAS instance URL, enabling header-injection-based phishing attacks that can harvest credentials. Exploitation requires user interaction and the CAS authentication configuration to be active; no public exploit or active exploitation has been identified at time of analysis.
Apache Syncope contains a Groovy sandbox bypass (CWE-94 code injection) that lets an administrator holding entitlements over the Implementations console register a malicious Groovy Command class whose untrusted code executes in a static CommandArgs initializer, escaping the intended script sandbox. Affected releases span 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2; exploitation requires a privileged, already-authenticated administrator account (CVSS 3.1 vector PR:H, score 6.5) rather than an anonymous attacker. There is no public exploit identified and the vulnerability is not in CISA KEV, but because Syncope is an identity governance and provisioning platform, successful abuse yields high confidentiality and integrity impact over managed identity data - CISA's SSVC assessment rates technical impact as 'total' while noting exploitation has not been observed and the attack is not automatable.
Apache Syncope, the Apache open-source identity governance and administration (IGA) platform, writes audit events to its configured audit store without adequately masking sensitive values carried in event payloads, so an operator with administrative access to that store can read credentials and other secrets that should have been redacted. All releases from 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2 are affected. The vulnerability is rated 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/C:H/I:N/A:N), is not listed in CISA KEV, and no public exploit code has been identified at time of analysis.
Sensitive information exposure in Apache Syncope allows a privileged administrator with Derived Schema entitlements to craft a malicious JEXL (Java Expression Language) expression that, when evaluated during User read operations, leaks LinkedAccount or Manager sensitive data - including hashed credentials - to any admin with User read access. Affected versions span three release lines: 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2. No public exploit code has been identified and CISA has not listed this in KEV; exploitation requires high-privilege access, limiting real-world risk to insider threats or compromised admin accounts.
Cross-site scripting in Apache Syncope's Console and Enduser login pages allows unsanitized HTML and JavaScript to be rendered via a maliciously crafted notification message link. Versions 4.0.4 through 4.0.7 and 4.1.0-M0 through 4.1.2 are affected. An attacker who can deliver a crafted HTTP link to a Syncope user can execute arbitrary JavaScript in that user's browser upon visiting the login page, enabling session hijacking, credential theft, or UI redress attacks.
Incorrect authorization enforcement in Apache Doris lets any authenticated user read data they were never granted privileges to access, breaking tenant and role isolation in the MPP database. The flaw affects the 2.0.x–2.1.x, 3.0.x, 4.0.0–4.0.7 and 4.1.0–4.1.3 lines, is remotely reachable by any low-privileged account without user interaction, and is rated CVSS 6.5 with confidentiality-only impact. Apache has published fixed releases 4.0.8 and 4.1.4; no public exploit code and no confirmed active exploitation were identified in the available intelligence.
The Storm UI topology REST endpoint (`GET /api/v1/topology/{id}`) in Apache Storm 3.0.0 returned a merged Nimbus daemon and topology configuration without credential redaction, exposing ZooKeeper authentication payloads and TLS keystore/truststore passwords to any principal holding topology read-only access. This privilege gap is significant because the dedicated `getNimbusConf` API already redacted these secrets and required elevated `nimbus.users` membership, yet the topology page - which merges in strictly more daemon state - was unprotected. No public exploit is identified at time of analysis, but exploitation requires only a single authenticated HTTP GET call, making the effective complexity trivially low for any principal with read-only cluster access.
Authorization bypass in Apache Storm Logviewer 3.0.0 exposes daemon logs and tenant log file listings to any filter-authenticated user, entirely disregarding the configured `logs.users` and `logs.groups` access controls. A boolean short-circuit in the daemon log authorization path discards the authorizer's decision whenever the daemon-log flag is set, and the daemon log page and download endpoints are reached without consulting an authorizer at all; additionally, the listing endpoints `/listLogs` and `/searchLogs` accept a user argument but never apply it. On a multi-tenant Storm cluster, any user who passes the servlet filter can read nimbus.log, supervisor.log, and other daemon logs-which contain co-tenant topology names, job owners, and configuration fragments-and enumerate all worker log file names. No public exploit identified at time of analysis.
Two authorization and redaction failures in Apache Storm 3.0.0 expose credential-bearing cluster configuration to under-privileged or entirely ungated callers. The Nimbus `getNimbusConf` Thrift API serves the full daemon configuration-including ZooKeeper authentication payloads and TLS keystore and truststore passwords-after only a user-level authorization check, silently omitting the credential masking applied everywhere else in the product. The Storm UI REST endpoint `/api/v1/cluster/configuration` is worse: the missing `@AuthNimbusOp` annotation causes the authorization filter to treat the endpoint as ungated, proxying requests under the UI daemon's own principal so that any caller passing `ui.filter` receives the full unredacted configuration regardless of their privilege level. No public exploit has been identified and this CVE is not in CISA KEV.
Log field injection in morgan, the Node.js HTTP request logger middleware, before version 1.12.1 allows unauthenticated remote attackers to manipulate parsed log records by embedding unescaped double quotes in HTTP headers such as User-Agent or Referer. The escapeLogField() function failed to escape the double-quote character, which serves as a field delimiter in the Apache combined log format that morgan emits by default, enabling a downstream log consumer that parses by field position to read attacker-supplied text as a subsequent field. In custom log formats that quote an attacker-controlled token before a server-controlled one, an attacker can forge field values including the HTTP response status code as seen by SIEMs, audit pipelines, or compliance tooling. No public exploit has been identified at time of analysis.
Denial of service in Apache ActiveMQ Artemis and Apache Artemis allows an authenticated client to exhaust shared broker thread resources by attaching a consumer with a crafted wildcard message selector that triggers excessive computational evaluation during message delivery. Affected versions span Apache ActiveMQ Artemis 1.0.0-2.44.0 and Apache Artemis 2.50.0-2.56.0, with a vendor-confirmed fix released in version 2.57.0 on September 9, 2026. No public exploit code or active exploitation has been identified at time of analysis.
Denial of service in Apache ActiveMQ Artemis and Apache Artemis message brokers allows authenticated clients holding MANAGE permission to crash broker processing threads by submitting crafted management-via-messaging requests that trigger unsafe Java deserialization. The deserializer processes method parameters the broker never actually uses, permitting gadget-chain payloads that consume excessive CPU and pin the thread pool. Both the legacy ActiveMQ Artemis lineage (1.3.0-2.44.0) and the newer Apache Artemis project (2.50.0-2.56.0) are affected; no public exploit or active exploitation has been identified at time of analysis.
Server-side request forgery in Apache Impala 2.0.0 through 4.5.1 allows SQL-authenticated users to coerce the Impala daemon into issuing arbitrary HTTP or file-system GET requests by specifying a malicious URL in the `avro.schema.url` table property. Internal service responses reachable by Impala but not directly by the attacker are partially exposed through SQL parsing error messages, enabling internal network reconnaissance, cloud metadata enumeration, and local file disclosure. Reported by zhaokaifei of ChinaTelecom, the vulnerability is resolved in version 4.5.2; no public exploit code or CISA KEV listing has been identified at time of analysis.
Stored cross-site scripting in Apache SkyWalking's Booster UI dashboard widget rendering (versions 10.2.0 through 10.4.0) allows an attacker with dashboard-edit access to inject persistent JavaScript that executes in the browser of any user viewing the affected dashboard. This is an incomplete remediation of CVE-2025-54057, meaning the original patch left residual unsanitized widget input paths. No public exploit code or active exploitation has been identified at time of analysis, though the prior CVE's public disclosure increases the likelihood of targeted research against the remaining surface.
Apache SkyWalking's PagerDuty alarm hook in versions 9.6.0 through 10.x transmits the PagerDuty integration routing key inside an unencrypted HTTP POST body before any redirect response from PagerDuty's HTTPS-only endpoint is received. Because the initial TCP socket write occurs in plaintext prior to the 301/302 redirect, a passive eavesdropper or MITM attacker positioned between the SkyWalking host and PagerDuty's API can capture the routing key verbatim from network traffic. No public exploit code has been identified and no active exploitation is confirmed; the practical impact is unauthorized PagerDuty event submission using the stolen credential, enabling false incident creation or alert fatigue rather than system compromise.
Stored cross-site scripting in Apache Allura allows authenticated repository contributors to inject persistent JavaScript payloads through code repository content, executing in the browsers of any user who subsequently views the affected forge pages. All releases through 1.20.0 of this open-source software forge platform are vulnerable. The Apache Security Team released version 1.21.0 in September 2026 to address this issue, as credited to researcher n0mi1k via the oss-security mailing list; no public exploit code has been identified at time of analysis.
Stored cross-site scripting via markdown HTML processing in Apache Allura through 1.20.0 permits an authenticated attacker to inject persistent malicious scripts that execute in the browsers of other users who view the compromised content - wikis, ticket comments, blog posts, or discussion threads. The vulnerability stems from insufficient sanitization of HTML embedded within markdown-rendered content across the forge platform's collaborative features. The Apache Software Foundation has released version 1.21.0 as the fix; no public exploit code or CISA KEV listing has been identified at time of analysis.
Control-character (newline) injection in Yoast SEO Premium before 27.6.1 allows an authenticated WordPress Author to write arbitrary Apache directives into the site's root .htaccess file via unsanitized redirect origins in file-based redirect mode. On Apache servers that process PHP directives, the injected auto_prepend_file directive can be chained with a polyglot image upload (available to Author-role users) to achieve full Remote Code Execution as the web server process. A public exploit is available via WPScan, making real-world exploitation feasible wherever the three required conditions align.
Stored XSS in the Apache Spark History Server (versions 3.0.0 through 3.5.7) allows a user with Spark job submission rights to inject unsanitized HTML/JavaScript into the History Server web UI via the application name field (spark.app.name), which executes in the browser of any higher-privileged user who subsequently views that job's history page. Apache rates this low severity due to layered prerequisites - the attacker must hold job submission rights and socially engineer an administrator into visiting the History Server. No public exploit has been identified at time of analysis; the vendor-released fix is Spark 3.5.8.
Unauthenticated network attackers can elicit Java stack traces from Red Hat IdM's Dogtag CA REST enrollment endpoint (POST /ca/rest/certrequests) by submitting malformed requests, causing HTTP 500 responses that expose internal implementation details under CWE-209. The same error path simultaneously amplifies the CA debug log with large multi-line stack traces, creating a log-fill resource exhaustion vector that drives disk growth and I/O contention on affected RHEL 6 through 10 deployments. No public exploit has been identified at time of analysis, but the attack requires no authentication and low complexity, making it accessible to unskilled opportunistic attackers targeting IdM infrastructure.
Cross-site scripting in Apache Wicket's AbstractSingleSelectChoice base class allows injection of unescaped HTML into the default/null option of DropDownChoice form elements. Affected versions span all supported Wicket branches from 8.0.0 through 10.10.0, as well as unsupported releases back to 1.5.0. An attacker who can influence the value returned by the overridden getNullValidDisplayValue() or getNullKeyDisplayValue() methods, or who controls the relevant resource bundle entries, can execute arbitrary JavaScript in a victim user's browser. No public exploit has been identified at time of analysis.
Cross-site scripting in Apache Wicket's Palette component allows injection of arbitrary HTML attributes into rendered `<option>` tags when applications override specific attribute-extension methods with attacker-influenced data. Affected are `wicket-extensions` versions spanning the 8.x, 9.x, and 10.x release lines; applications relying on the default method implementations are definitively not affected. Vendor-released patches are available at versions 8.19.0, 9.24.0, and 10.11.0; no public exploit code or CISA KEV listing has been identified at time of analysis.
Cross-site scripting in Apache Wicket's MetaDataHeaderItem class allows injection of arbitrary HTML attributes into generated <meta> and <link> header tags when applications pass attacker-influenced data to the addTagAttribute, forMetaTag, or forLinkTag APIs. The flawed escaping logic - replacing double-quote characters with backslash-double-quote, which carries no escaping semantics in HTML - permits a double-quote in an attacker-controlled value to break out of the attribute context and inject additional attributes such as JavaScript event handlers. Affected release lines span 8.0.0-8.18.0, 9.0.0-9.23.0, and 10.0.0-10.10.0; no public exploit has been identified at time of analysis.
Cross-site scripting in Apache Wicket's AutoLabelTextResolver allows injection of arbitrary markup into web pages when attacker-controlled data reaches a form component's label model via FormComponent#setLabel(IModel). The resolver, registered by default in every WebApplication, writes label values directly into rendered markup without any escaping and ignores the escape-model-strings application setting entirely - meaning there was no available configuration workaround. Applications are vulnerable wherever user-influenced data flows into a label model; this includes both stored XSS (data retrieved from a database) and reflected XSS (data sourced from the current request). No public exploit has been identified at time of analysis, but the vulnerability affects all supported release lines and all unsupported releases from 1.5.0 onwards.
Cross-site scripting in Apache Wicket's Button component allows injection of arbitrary markup into rendered pages when the button is bound to a `<button>` HTML element whose model contains attacker-influenced data. The root cause is an intentional design choice - Button's constructor clears the escape-model-strings flag to prevent double-encoding of `<input>` attribute values - that becomes a security flaw in the `<button>` rendering path, where element body content is never encoded by ComponentTag. Subclasses AjaxButton, AjaxFallbackButton, and WizardButton inherit the same constructor and are equally affected; no public exploit or CISA KEV listing is recorded at time of analysis.
Cross-site scripting vulnerabilities in Apache Wicket's AjaxEditableChoiceLabel and related wicket-extensions components allow an attacker who can influence rendered choice or model data to inject arbitrary HTML or JavaScript into page markup, executing in the browser of any user viewing the affected page. Versions 8.0.0 through 8.18.0, 9.0.0 through 9.23.0, and 10.0.0 through 10.10.0 of the org.apache.wicket:wicket-extensions module are confirmed affected. The root cause is that two distinct rendering paths bypass Wicket's default HTML escaping, and the escapeModelStrings configuration property has no corrective effect on these components. No public exploit has been identified at time of analysis.
Cross-site request forgery protection bypasses in Apache Wicket's ResourceIsolationRequestCycleListener allow network attackers to execute authenticated listener actions - link callbacks, form submits, behavior endpoints - on behalf of logged-in users across versions 9.1.0-9.23.0 and 10.0.0-10.10.0. The default FetchMetadataResourceIsolationPolicy incorrectly permits cross-site top-level GET navigations (exploitable because Wicket routes Link.onClick() and form callbacks through ordinary browser navigations) and unconditionally trusts Sec-Fetch-Site: same-site requests from sibling origins - both vectors deliver the victim's SameSite=Lax session cookie to the targeted listener. No public exploit has been identified at time of analysis; vendor-released patches are available in versions 9.24.0 and 10.11.0.
Path traversal in Apache Wicket's package resource URL handling exposes files outside the intended package directory to unauthenticated remote attackers, including files under WEB-INF that servlet containers ordinarily protect from direct access. Affected are all releases from 8.0.0 through 8.18.0, 9.0.0 through 9.23.0, and 10.0.0 through 10.10.0. Under default configuration the readable file set is bounded by the SecurePackageResourceGuard's extension allowlist (excluding .xml, .properties, .class), but all configurations unconditionally expose a path-existence oracle usable for reconnaissance, and applications using looser guard configurations can disclose web.xml and other sensitive configuration files. No public exploit identified at time of analysis.
Server-Side Request Forgery (SSRF) in Apache Shiro's Jakarta EE integration module (shiro-jakata-ee) enables a low-privileged authenticated user to steer server-initiated POST requests to an attacker-controlled host and transmit attacker-controlled data. Versions 2.0.0-alpha-0 through 3.0.0 of the shiro-jakata-ee artifact are affected, but only when the Jakarta EE integration module is deployed - the 1.x line and non-Jakarta-EE deployments are not vulnerable. No public exploit has been identified at time of analysis, and vendor-released patch 3.0.1 is available as of 2026-08-24.
Denial-of-service in Spring for Apache Kafka's `DeadLetterPublishingRecovererFactory` exposes consumer JVMs across all supported branches (2.8.x through 4.1.0) to crash or hang when processing messages with a crafted `retry_topic-original-timestamp` header. An authenticated Kafka producer can inject a ConsumerRecord carrying an oversized or malformed header byte array, which is passed without any length or format validation directly to Java's `BigInteger(byte[])` constructor, triggering heap memory exhaustion or an unhandled exception that disrupts message consumption. No public exploit code has been identified and the CVE does not appear in CISA KEV at time of analysis, but low attack complexity combined with broad version coverage makes this a credible availability threat for any Spring Kafka deployment using retry or dead-letter queue features.
Header type injection in Spring for Apache Kafka's default mapper configuration allows any Kafka producer with access to a consumed topic to inject java.net.InetAddress objects through the spring_json_header_types message header, triggering DNS resolution on the consumer host. All applications using @KafkaListener with the default JsonKafkaHeaderMapper or DefaultKafkaHeaderMapper - spanning versions 2.8.x through 4.1.0 - are affected without any non-default configuration required. No public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV.
Authorization bypass and privilege escalation in Apache APISIX 3.11.0-3.17.0 stem from the `attach-consumer-label` plugin failing to strip client-supplied consumer-label headers before using them in security decisions. An attacker who can reach the gateway can forge header values to impersonate a higher-privileged consumer label, bypassing route-level access controls. No vendor-released patch is available at time of analysis (fix version marked pending); no public exploit code or CISA KEV listing has been identified.
Insufficient session expiration in Apache Tomcat allows an authenticated attacker to maintain an active WebSocket connection after the underlying HTTP session has been invalidated, violating the Jakarta WebSocket specification's requirement that WebSocket sessions close when their parent HTTP session ends. Affected are all supported branches from 9.0.0.M1 through 9.0.120, 10.1.0-M1 through 10.1.57, and 11.0.0-M1 through 11.0.24, plus EOL branches 7.0.43-7.0.109 and 8.5.0-8.5.100. No public exploit or CISA KEV listing has been identified at time of analysis, and the low EPSS score (0.28%, 19th percentile) reflects limited real-world exploitation probability.
Unrestricted Solr query syntax passthrough in the TYPO3 EXT:solr enterprise search extension exposes indexed data to remote unauthenticated attackers via blind injection techniques. By crafting queries that exploit Solr's native field selectors, wildcards, and range operators, an attacker can enumerate schema field names and systematically extract stored values without triggering obvious errors. No public exploit code has been identified at time of analysis; the CVSS 4.0 score of 6.3 reflects high attack complexity (AC:H/AT:P) that limits opportunistic mass exploitation.
Unauthenticated REST API disclosure in Apache Allura through version 1.19.1 exposes certain content items to unauthorized actors without any credentials. The vulnerability stems from insufficient access control on REST endpoints, allowing any network-accessible client to retrieve content that should require authentication. No public exploit or CISA KEV listing has been identified at time of analysis, but the low exploitation barrier (unauthenticated, network-accessible) makes this a straightforward information leakage risk for any publicly exposed Allura instance.
Header injection via structured-mode CloudEvents in Apache Camel's Knative consumer enables unauthenticated SSRF, path traversal, and message-dispatch redirection against routes that forward to header-driven components. The flaw exists because CloudEvent extension fields in structured content mode (Content-Type: application/cloudevents+json) are copied directly into Camel Exchange headers without applying the KnativeHttpHeaderFilterStrategy that correctly guards the binary content-mode path - an incomplete fix of the same filter-bypass pattern addressed across multiple related CVEs (CVE-2025-27636, CVE-2025-29891, CVE-2025-30177, CVE-2026-40453, CVE-2026-47323). No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface - unauthenticated HTTP POST to a Knative endpoint - requires no special tooling.
Path traversal in Apache Camel's camel-azure-storage-datalake component allows anyone with write access to a consumed Azure Data Lake Storage Gen2 filesystem to direct the Camel process to write or overwrite files at arbitrary locations on the local filesystem. The downloadToFile operation constructs local paths by joining the configured fileDir with the remote file name exactly as returned by the Azure SDK - without lexical normalization or any boundary check - meaning a remote path name containing parent-directory segments (e.g., '../../etc/cron.d/payload') resolves outside fileDir. Depending on what the Camel process can write, this integrity violation can escalate to code execution or service disruption. No active exploitation has been identified at time of analysis, and vendor-released patches are available in versions 4.14.9, 4.18.4, and 4.22.0.
MIME header injection in Apache Camel's camel-mail MimeMultipart data format allows unauthenticated network senders to plant Camel-internal namespace headers onto the Camel Exchange when headersInline is set to true, potentially redirecting what downstream route components - such as camel-sql - execute. Versions 2.17.0 through 4.14.8, 4.15.0 through 4.18.3, and 4.19.0 through 4.21.x are affected across all release lines until the current fixes. No public exploit code or active exploitation has been identified; EPSS sits at 0.16% and SSVC rates exploitation status as none, making this a patch-priority rather than emergency-response item for most organizations.
Heap exhaustion via unbounded memory leak in micrometer-core affects Java applications using Apache HttpAsyncClient (4.x or 5.x) instrumented with MicrometerHttpClientInterceptor. When asynchronous HTTP requests fail before receiving any server response - due to connection resets, network timeouts, or unreachable endpoints - the per-request tracking state allocated by the interceptor is never released, accumulating indefinitely on the JVM heap. Sustained failure conditions (such as a misbehaving or attacker-controlled upstream server) can drive heap exhaustion to OutOfMemoryError, crashing the instrumented application. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Session cookie forgery in Apache::AppSamurai::Util through version 1.01 is possible because CreateSessionAuthKey derives its entire entropy from observable runtime state - wall-clock microseconds and the Apache worker process ID - rather than a cryptographically secure random source. An unauthenticated remote attacker who can bound the second in which a target session was created and enumerate the small PID space can construct candidate 64-character hex cookies and recover a valid session token through online brute-force, bypassing authentication for all resources protected by the module. No public exploit code has been identified and SSVC confirms no current exploitation, though the attack is mechanically feasible given the constrained key space.
Resource exhaustion in Apache CloudStack's scoped global configuration subsystem-spanning versions 4.7.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0-allows authenticated low-privilege users to gradually trigger a denial-of-service condition against the management server. The vulnerability (CWE-772) affects multiple plugins including Quota and Host-HA, which allocate resources during configuration operations but fail to release them after their effective lifetime. No public exploit or active exploitation has been identified; vendor-released fixes are available in 4.20.3.1 and 4.22.1.1.
Improper output encoding in Apache CloudStack's management UI exposes administrators to cross-site scripting (XSS) when using the Lock User functionality across versions 4.20.0.0-4.20.3.0 and 4.21.0.0-4.22.1.0. A low-privilege user can embed a malicious script payload in a user-controlled field; when an administrator invokes the Lock User workflow, the CloudStack UI renders the payload without proper HTML or JavaScript escaping, executing it in the admin's browser session. No public exploit or CISA KEV listing has been identified at time of analysis, but the potential for admin session hijacking makes this a meaningful risk in multi-tenant environments.
Pre-validation SSRF in Apache CloudStack's template and ISO registration allows authenticated users to trigger HTTP HEAD/GET requests to arbitrary URLs - including internal network resources - before URL validation is applied. Affected versions are 4.20.3.0 and 4.21.0.0 through 4.22.1.0; vendor-released patches exist in 4.20.3.1 and 4.22.1.1. No public exploit code or active exploitation has been identified at time of analysis, and exploitation requires valid CloudStack credentials with template-registration privileges.
Sensitive information exposure in Apache CloudStack's Webhook module allows unauthorized actors to view data they should not have access to during webhook delivery listing and deletion operations. Affected deployments span versions 4.20.0.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0, covering two active release trains. No public exploit or active exploitation has been identified at time of analysis; vendor-released patches are available.
Missing authorization in Apache CloudStack's listHostTags API allows domain administrators to enumerate host tags across all domains in a multi-tenant deployment, violating tenant isolation boundaries established by the domain hierarchy. Affected versions span 4.12.0.0 through 4.22.1.0 across two release trains, with vendor-released patches in 4.20.3.1 and 4.22.1.1 confirmed by the Apache security advisory. No public exploit code exists and the vulnerability is not listed in CISA KEV, but the risk is meaningful in shared, multi-tenant CloudStack environments where cross-domain host tag visibility undermines infrastructure confidentiality guarantees between tenants.
Improper access control in Apache CloudStack's annotation APIs (addAnnotation and listAnnotation) allows any authenticated user to read and write annotations on entities they do not own. The APIs perform an ownership check when an entity UUID is supplied but fail to enforce the result of that check, reducing authorization to a formality that any authenticated user can bypass. No public exploit has been identified at time of analysis; no EPSS or CISA KEV data is available, but the bug affects all CloudStack deployments from 4.15.0.0 onward until the patched releases.
Server-Side Request Forgery in Apache InLong Manager (versions 2.0.0-2.3.x) allows any authenticated user - no administrative role required - to coerce the Manager service into issuing outbound HTTP requests or TCP connections to arbitrary internal hosts and ports. This effectively turns the InLong Manager into an open proxy for internal network reconnaissance, enabling access to otherwise firewalled services such as cloud instance metadata endpoints, internal APIs, or database management interfaces. No public exploit has been identified at time of analysis, but the low privilege bar makes this broadly reachable within any deployment that permits shared user access.
Uncontrolled Resource Consumption (CWE-400) in Apache InLong versions 2.0.0 through 2.3.x exposes two related attack surfaces: authenticated users can trigger excessive resource consumption to degrade service availability, and the same pathway permits upload of non-official packages, introducing a package-integrity risk alongside the denial-of-service vector. Affected deployments running any release in the 2.0.0-2.3.x range should treat this as a priority upgrade given the dual nature of the flaw. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Unauthorized template information disclosure in Apache InLong 2.0.0 through 2.3.x allows authenticated users who are not designated template responsible persons to view template configurations they should not have access to. The CVE is tagged CWE-400 (Uncontrolled Resource Consumption) and classified as Denial of Service, yet the description describes an access control bypass - this is a data contradiction that analysts should flag before making control decisions. No public exploit or active exploitation has been identified. Vendor fix is available in Apache InLong 2.4.0.
Cross-request data leakage in Apache Struts 7.2.1's JSON plugin allows an authenticated remote attacker to observe response content associated with a concurrent request belonging to a different user. The root cause is a thread-safety defect (CWE-567) in the SMD/JSON-RPC interceptor, where per-response serialization state is not isolated between concurrent requests. Exploitation is constrained to the non-default SMD/JSON-RPC mode of the JSON interceptor; no public exploit code has been identified at time of analysis, and the EPSS score of 0.15% (4th percentile) reflects the limited realistic exploitation surface.
Cross-request data exposure in the Apache Struts JSON plugin (version 7.2.1) results from per-request parsing state being improperly shared across concurrent requests, enabling information observable in one user's session to leak into another's. Authenticated remote attackers targeting applications that have explicitly enabled JSON action population can exploit this concurrency flaw (CWE-567) to read partial request data or circumvent configured parsing limits. With an EPSS of 0.15% (4th percentile), no CISA KEV listing, and no public exploit identified at time of analysis, real-world risk is low and narrowed further by the non-default plugin requirement.
Cross-site scripting in Apache Allura's Markdown rendering (versions 1.10.0 up to but not including 1.19.1) allows an attacker to inject script-related HTML into content that other users view, executing arbitrary JavaScript in their browsers. Because Allura is a collaborative forge where users routinely post Markdown in tickets, wiki pages, and comments, the payload is most likely stored and delivered to victims who open the affected page. No public exploit identified at time of analysis, and there is no CISA KEV listing or POC signal; the Apache PMC has released version 1.19.1 as the fix.
Cross-site scripting (XSS) in Apache Allura's code-display feature allows an attacker who can place crafted content into a rendered code view to execute arbitrary JavaScript in the browser of any user who views that code, in all versions before 1.19.1. Because Allura is forge/project-hosting software, a successful attack can hijack the sessions of project members or administrators. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Insecure Direct Object Reference (IDOR) in Apache Allura before 1.19.1 allows unauthorized access to multiple Artifact types due to missing server-side permission checks. Attackers who can interact with the platform can reference artifact objects directly by their identifiers and retrieve content beyond their authorization level, resulting in information disclosure across potentially broad artifact categories. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Secret exposure in Apache Airflow's Rendered Templates UI allows any authenticated user with task-level view access to read plaintext credential values that should have been masked. The secrets masker's `isinstance(str)` guard silently skips dict-typed Python objects, meaning JSON Variables accessed via `var.json` and containing dict payloads (e.g., database credentials, API keys stored as structured JSON) are rendered in cleartext rather than redacted. No public exploit is identified at time of analysis; however, the disclosure requires nothing more than standard UI navigation by a legitimately authenticated user.
Unsafe deserialization in Apache Airflow's XCom REST API allows an authenticated user with XCom write-and-read access to instantiate arbitrary `airflow.*` classes on the API server by smuggling reserved serialization keys inside JSON string literals. The `_check_forbidden_xcom_keys` guard inspected `dict`, `list`, and `tuple` types but did not attempt to JSON-decode `str` values, so a payload like `json.dumps({"__classname__": "airflow.sdk.definitions.connection.Connection"})` passed the write-time check and was later reconstructed into a live Python object when read back via `?deserialize=true`. No public exploit has been identified at time of analysis; vendor-released patch is available in apache-airflow 3.3.1.
Sensitive values stored as deeply nested lists, tuples, or sets in Apache Airflow Variables are displayed unmasked in the Variables UI due to a recursion-depth logic error in the secrets masker. This is an incomplete-fix follow-up to CVE-2026-42358: that prior fix made dictionary traversal unbounded but left list/tuple/set structures subject to the depth cutoff, allowing values beyond that depth to appear in plaintext on screen. The practical impact is narrow - any authenticated user who can see the Variable in the UI already has read access to the full value through the Variables REST API - making this a shoulder-surfing defense gap rather than an access-control bypass. No public exploit has been identified at time of analysis.
Sensitive credential exposure in Apache Airflow 3.3.0 allows an authenticated Viewer with configuration-read access to retrieve team-scoped sensitive options - including Celery broker URLs with embedded credentials - in cleartext via the Config API. The secrets masker evaluated sensitivity against raw section names without resolving team-prefixed sections (e.g., [team_a=celery]) back to their registered base section, so team-scoped overrides silently bypassed masking while equivalent global options were correctly redacted. This is a third distinct masker bypass variant following CVE-2026-48828 and CVE-2026-48892, meaning deployments that already upgraded to 3.3.0 to remediate those issues remain exposed. No public exploit identified at time of analysis.
Cleartext secret exposure in Apache Airflow's audit log affects all versions before 3.3.1, allowing any authenticated user with audit-log read access to recover Variable values and Connection `extra` credentials verbatim - without holding Variables or Connections read permissions. The bulk API endpoints (`PATCH /api/v2/variables`, `PATCH /api/v2/connections`) bypassed audit-log masking because the masker inspected only top-level request fields while bulk payloads nest entities two levels deep under `actions[].entities[]`. The Airflow UI's Import Variables action posts to this same bulk endpoint, meaning a routine operator import silently writes every secret in the uploaded file to the unmasked audit log. No public exploit is identified at time of analysis, but the vulnerability is fully exploitable by any authenticated user with log access, and deployments that upgraded to 3.3.0 in response to the related CVE-2026-50204 remain vulnerable and must upgrade again.
Cleartext exposure of list-shaped Variable secrets in Apache Airflow Task SDK (all versions before 3.3.1) allows any authenticated Airflow user to recover sensitive values directly from task execution logs and the Rendered Templates UI. The masking logic in _mask_and_deserialize_variable correctly handled string- and dict-typed JSON Variable values but contained no branch for the list type, so arrays - which may hold passwords, API tokens, or connection strings - were returned unredacted. No public exploit has been identified at time of analysis; however, organizations that patched CVE-2026-59244 remain fully exposed because that fix addressed only the dict case, and must upgrade again to 3.3.1.
Cross-team DAG authorization bypass in Apache Airflow versions prior to 3.3.1 allows authenticated users in one team to trigger DAG runs and read XCom values belonging to other teams. The asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom check in wait_dag_run_until_finished both passed DagDetails without resolving the DAG's team_name, causing team-aware auth managers (e.g., Keycloak) to evaluate the permission against the global DAG resource instead of the team-scoped DAG:<team> resource. This is a missing authorization flaw (CWE-862) affecting only deployments running multi-team mode with a team-aware auth manager; FAB auth manager deployments are explicitly unaffected. No public exploit code or CISA KEV listing has been identified at time of analysis.
Cross-team credential access in Apache Airflow before 3.3.1 allows authenticated members of one team to invoke another team's Connection credentials through the POST /api/v2/connections/test API endpoint, exploiting a broken namespace-isolation guard in the environment-variable secrets backend. The flaw-confirmed by Apache with patches in PRs #70736 and #70902-combines a guard that only triggered on unscoped (global) requests with a regex incapable of matching team names containing underscores, even though underscores are explicitly permitted in Airflow team name validation. Exploitation requires a precise configuration alignment of multi_team mode, an explicitly enabled test_connection endpoint, and environment-variable-provisioned team secrets; no public exploit has been identified at time of analysis.
Cross-team credential disclosure in the Apache Airflow Google Provider's Cloud Secret Manager backend exposes every team's Connections and Variables to every other team in multi-team deployments. The backend's public methods accepted a team_name parameter but silently discarded it before the internal secret lookup, collapsing all team namespaces into one shared, unscoped lookup. No public exploit has been identified at time of analysis; the vendor-released fix is apache-airflow-providers-google 22.3.0.
Cross-team secret disclosure in Apache Airflow Amazon Provider (all versions before 9.34.0) allows an authenticated Airflow team member to read Connections, Variables, or Configuration secrets belonging to a different team in a multi-team deployment. By crafting a lookup ID that embeds the '--' team namespace separator, an attacker causes the provider's team-scoped lookup to miss and the pre-patch team-agnostic fallback to resolve the target team's AWS Secrets Manager or SSM Parameter Store secret in plaintext. No public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV, but the exploit technique is mechanically straightforward given the documented '--' naming convention.
Cross-team secret disclosure in Apache Airflow's Yandex Lockbox secrets backend exposes one team's credentials to members of a different team in multi-team deployments. Any authenticated Airflow user belonging to any team can retrieve connections or variables owned by another team by supplying a secret ID that embeds the target team's namespace separator sequence. The flaw requires only that multi-team mode and the Yandex Lockbox backend are active - both standard, documented configurations - and yields full plaintext credential exposure. No public exploit or CISA KEV listing exists at time of analysis.
Cross-team credential disclosure in the Apache Airflow Microsoft Azure provider's Key Vault secrets backend allows any authenticated team member to read credentials belonging to a different team in multi-team deployments running versions prior to 14.1.0. The backend's team-scoped lookup falls through to a team-agnostic resolution when the scoped lookup misses, and an attacker in one team can deliberately trigger this by supplying a connection or variable ID whose normalized form encodes the target team's namespace prefix. No public exploit has been identified at time of analysis, but the attack primitive is directly derivable from the published patch diff, making this a credible insider-privilege escalation risk for any organization using this backend in multi-team mode.
JWT tokens written to Apache Ranger logs in versions 2.8.0 and earlier remain replayable, allowing any party with read access to those logs to authenticate as legitimate users without knowing their credentials. The flaw (CWE-532) is particularly severe because Ranger controls data security policies across Hadoop ecosystems - impersonating a Ranger user can yield control over access policies for HDFS, Hive, HBase, and related services. No public exploit or CISA KEV listing exists at time of analysis; Apache has confirmed a fix in version 2.9.0.
Traefik's BasicAuth middleware in versions 3.6.11-3.6.24 and 3.7.0-3.7.9 permits an authenticated low-privilege user to forge arbitrary backend identities via a singleflight key collision race condition. By concatenating their known valid password with a retrieved stored bcrypt hash, an attacker crafts a singleflight deduplication key identical to a legitimate in-flight request's key; the middleware returns the legitimate request's successful authentication result to the attacker's request, then propagates the attacker's chosen unconfigured username to the backend as a trusted identity. A fully working proof-of-concept achieving 25-of-25 successful identity forgeries under default bcrypt cost is publicly available in the GitHub security advisory; no CISA KEV listing has been identified at time of analysis.
Apache Polaris incorrectly enforces storage location boundaries during Iceberg table and view registration, enabling an authenticated principal with registration privileges to cause the catalog service to read S3 objects outside the configured allowed storage perimeter. Exploitation depends on a deployment running S3 credential vending where the catalog's underlying credentials can access objects beyond the allowed boundary - a constrained but realistic enterprise configuration. The demonstrated impact is limited to partial confidentiality disclosure of out-of-bounds objects; no unauthorized write or availability impact has been demonstrated, and no public exploit or active exploitation has been identified at time of analysis.
Improper authorization in Apache Answer through version 2.0.1 allows any authenticated user to reject arbitrary pending edit-revisions without holding review permissions. The missing authorization check on the reject operation means content moderation controls are effectively bypassed by ordinary users, enabling disruption of the peer-review workflow. No public exploit code exists and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Directory traversal vulnerability in the fileserver upload/download functionality for blob messages in Apache ActiveMQ 5.x before 5.11.2 for Windows allows remote attackers to create JSP files in. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 86.0%.
GNU Bash through 4.3 bash43-026 does not properly parse function definitions in the values of environment variables, which allows remote attackers to execute arbitrary commands via a crafted. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 92.7%.
ParametersInterceptor in Apache Struts before 2.3.20 does not properly restrict access to the getClass method, which allows remote attackers to "manipulate" the ClassLoader and execute arbitrary code. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 91.4%.
The ParametersInterceptor in Apache Struts before 2.3.16.2 allows remote attackers to "manipulate" the ClassLoader via the class parameter, which is passed to the getClass method. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 93.1%.
Certain getText methods in the ActionSupport controller in Apache Roller before 5.0.2 allow remote attackers to execute arbitrary OGNL expressions via the first or second parameter, as demonstrated. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 87.0%.
Apache Struts 2.0.0 through 2.3.15 allows remote attackers to execute arbitrary OGNL expressions via a parameter with a crafted (1) action:, (2) redirect:, or (3) redirectAction: prefix. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2). Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, no authentication required. Public exploit code available and EPSS exploitation probability 87.6%.
Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2). Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 91.1%.
The DebuggingInterceptor component in Apache Struts before 2.3.1.1, when developer mode is used, allows remote attackers to execute arbitrary commands via unspecified vectors. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 92.6%.
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during certain exception handling for mismatched data types of properties, which. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Let me synthesize. CVE-2026-86465: Apache Airflow Akeyless provider secrets backend team-scope guard bypass via user-controlled key. Affected: apache-airflow-providers-akeyless before 0.3.1. Fix: 0.3.1. PR: https://github.com/apache/airflow/pull/72646. Similar class to Azure Key Vault, Yandex Lockbox, Amazon secrets backends CVEs. Multi-team deployments using Akeyless secrets backend; single-team not affected. Reachable from ordinary DAG code via Execution API Variables route accepting path-shaped key. DAG author scoped to one team can read secrets belonging to another team — info disclosure (cross-tenant secret access). CVSS: N/A provided. My assessed vector: PR:L (requires DAG author privileges / authenticated user), AV:N, AC:L, UI:N, S:C? Scope change — impacts another team's secrets, but scope change in CVSS terms means authorization scope. Cross-team boundary crossing could be S:C. Impact C:H, I:N, A:N. So CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. That's ~8.3? Let's compute: S:C base... Actually with S:C, PR:L: exploitability = 8.22*AV(0.85)*AC(0.77)*PR(0.68)*UI(0.85) = 8.22*0.85=6.987; *0.77=5.380; *0.68=3.658; *0.85=3.110. Impact: ISCBase = 1 - (1-C)(1-I)(1-A) = 1 - (1-0.56)(1)(1) = 0.56. Scope changed: Impact = 7.52*(ISC-0.029) - 3.25*(ISC-0.02)^15 = 7.52*(0.531) - 3.25*(0.54)^15 ≈ 3.993 - ~0 = 3.993. Base = roundup(min(1.08*(3.110+3.993),10)) = roundup(7.67) = 7.7. Hmm, 7.7 High. Maybe S:C is arguable. Alternatively S:U with C:H gives: Impact = 6.42*0.56 = 3.595; exploitability 3.110; base = roundup(min(1.08*6.705,10)) = roundup(7.24)=7.3. Either way ~7.3-7.7. Actually, "moderate" severity per Apache. Hmm. Apache's own severity is "moderate". But my assessment... I'll go with S:C? Let's think: the vulnerable component is the Akeyless backend; the impact is a different team's secrets. CVSS scope change refers to impact on components beyond the vulnerable component's security authority. The secrets backend... Hmm. This is a classic cross-tenant autho
Stale database-backed sessions in the Apache Airflow FAB provider (apache-airflow-providers-fab 3.2.0 before 3.9.0) allow an attacker who already holds a copy of a victim's session cookie to keep full access to that account even after the account password is changed, because the Admin user-edit PATCH endpoint never calls the session-invalidation helper. This is a second, independent route to the outcome partially addressed by CVE-2026-82311, so deployments that only applied that earlier fix remain exposed and must additionally upgrade to 3.9.0 or later. No public exploit code or active exploitation is identified from the available data; severity is rated moderate by the vendor.
Password changes made through the Apache Airflow FAB provider's Admin user-edit PATCH endpoint do not invalidate that user's existing database-backed sessions, so anyone already holding a copy of the victim's session cookie keeps full access to the account after the reset. The flaw affects apache-airflow-providers-fab 3.2.0 up to (but not including) 3.9.0 in deployments using the FAB auth manager with database-backed sessions, and it is a second, independent route to the outcome addressed by CVE-2026-82311 — applying that earlier fix alone does not remediate this endpoint. The advisory rates the issue moderate; no public exploit code, CISA KEV listing, or EPSS score was provided with the intelligence supplied.
The Apache Airflow Keycloak provider (apache-airflow-providers-keycloak before 0.10.0), when running on Airflow 3.3 or later, performs authorization using Keycloak access and refresh tokens read from separate, unsigned cookies while taking the user's identity from the signed Airflow session token, and never verifies that both describe the same subject. Any user
Path-name disclosure in Apache ZooKeeper 3.8.0 through 3.8.6 and 3.9.0 through 3.9.5 lets a connected client learn the names of ACL-restricted znodes by registering exists-watches on paths that do not yet exist and then reconnecting after those paths are created under restrictive ACLs. The reconnect replay handler DataTree.setWatches() delivers the watch notification with a null ACL, bypassing the ACL check that was added to WatchManager.triggerWatch() as the fix for CVE-2024-23944 (ZOOKEEPER-4799), making this an incomplete-fix bypass. Only the znode path string is exposed, not znode data, but because paths frequently embed usernames, login IDs, or tenant identifiers, Apache and the reporter rate it critical; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated topology submission in Apache Storm Nimbus 3.0.0 through 3.0.x allows any authenticated Storm user to read arbitrary files accessible to the Nimbus daemon by supplying a server-side path as the uploadedJarLocation argument to submitTopology or submitTopologyWithOpts, bypassing the intended beginFileUpload flow entirely. Nimbus copies the targeted file into a topology blob and automatically grants the submitter read access via blob ACLs, enabling retrieval of Kerberos keytabs, TLS private keys, and ZooKeeper credentials through standard blob download APIs. A proof of concept was submitted alongside disclosure; upgrade to Apache Storm 3.1.0 is the required remediation.
Open redirect in Apache Syncope's SRA (Secure Remote Access) component allows unauthenticated network attackers to redirect authenticated users to attacker-controlled URLs during CAS SSO login flows. The vulnerability arises because Syncope SRA unconditionally trusts client-supplied forwarded HTTP headers (e.g. X-Forwarded-Host, X-Forwarded-Proto) when constructing the target Apereo CAS instance URL, enabling header-injection-based phishing attacks that can harvest credentials. Exploitation requires user interaction and the CAS authentication configuration to be active; no public exploit or active exploitation has been identified at time of analysis.
Apache Syncope contains a Groovy sandbox bypass (CWE-94 code injection) that lets an administrator holding entitlements over the Implementations console register a malicious Groovy Command class whose untrusted code executes in a static CommandArgs initializer, escaping the intended script sandbox. Affected releases span 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2; exploitation requires a privileged, already-authenticated administrator account (CVSS 3.1 vector PR:H, score 6.5) rather than an anonymous attacker. There is no public exploit identified and the vulnerability is not in CISA KEV, but because Syncope is an identity governance and provisioning platform, successful abuse yields high confidentiality and integrity impact over managed identity data - CISA's SSVC assessment rates technical impact as 'total' while noting exploitation has not been observed and the attack is not automatable.
Apache Syncope, the Apache open-source identity governance and administration (IGA) platform, writes audit events to its configured audit store without adequately masking sensitive values carried in event payloads, so an operator with administrative access to that store can read credentials and other secrets that should have been redacted. All releases from 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2 are affected. The vulnerability is rated 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/C:H/I:N/A:N), is not listed in CISA KEV, and no public exploit code has been identified at time of analysis.
Sensitive information exposure in Apache Syncope allows a privileged administrator with Derived Schema entitlements to craft a malicious JEXL (Java Expression Language) expression that, when evaluated during User read operations, leaks LinkedAccount or Manager sensitive data - including hashed credentials - to any admin with User read access. Affected versions span three release lines: 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2. No public exploit code has been identified and CISA has not listed this in KEV; exploitation requires high-privilege access, limiting real-world risk to insider threats or compromised admin accounts.
Cross-site scripting in Apache Syncope's Console and Enduser login pages allows unsanitized HTML and JavaScript to be rendered via a maliciously crafted notification message link. Versions 4.0.4 through 4.0.7 and 4.1.0-M0 through 4.1.2 are affected. An attacker who can deliver a crafted HTTP link to a Syncope user can execute arbitrary JavaScript in that user's browser upon visiting the login page, enabling session hijacking, credential theft, or UI redress attacks.
Incorrect authorization enforcement in Apache Doris lets any authenticated user read data they were never granted privileges to access, breaking tenant and role isolation in the MPP database. The flaw affects the 2.0.x–2.1.x, 3.0.x, 4.0.0–4.0.7 and 4.1.0–4.1.3 lines, is remotely reachable by any low-privileged account without user interaction, and is rated CVSS 6.5 with confidentiality-only impact. Apache has published fixed releases 4.0.8 and 4.1.4; no public exploit code and no confirmed active exploitation were identified in the available intelligence.
The Storm UI topology REST endpoint (`GET /api/v1/topology/{id}`) in Apache Storm 3.0.0 returned a merged Nimbus daemon and topology configuration without credential redaction, exposing ZooKeeper authentication payloads and TLS keystore/truststore passwords to any principal holding topology read-only access. This privilege gap is significant because the dedicated `getNimbusConf` API already redacted these secrets and required elevated `nimbus.users` membership, yet the topology page - which merges in strictly more daemon state - was unprotected. No public exploit is identified at time of analysis, but exploitation requires only a single authenticated HTTP GET call, making the effective complexity trivially low for any principal with read-only cluster access.
Authorization bypass in Apache Storm Logviewer 3.0.0 exposes daemon logs and tenant log file listings to any filter-authenticated user, entirely disregarding the configured `logs.users` and `logs.groups` access controls. A boolean short-circuit in the daemon log authorization path discards the authorizer's decision whenever the daemon-log flag is set, and the daemon log page and download endpoints are reached without consulting an authorizer at all; additionally, the listing endpoints `/listLogs` and `/searchLogs` accept a user argument but never apply it. On a multi-tenant Storm cluster, any user who passes the servlet filter can read nimbus.log, supervisor.log, and other daemon logs-which contain co-tenant topology names, job owners, and configuration fragments-and enumerate all worker log file names. No public exploit identified at time of analysis.
Two authorization and redaction failures in Apache Storm 3.0.0 expose credential-bearing cluster configuration to under-privileged or entirely ungated callers. The Nimbus `getNimbusConf` Thrift API serves the full daemon configuration-including ZooKeeper authentication payloads and TLS keystore and truststore passwords-after only a user-level authorization check, silently omitting the credential masking applied everywhere else in the product. The Storm UI REST endpoint `/api/v1/cluster/configuration` is worse: the missing `@AuthNimbusOp` annotation causes the authorization filter to treat the endpoint as ungated, proxying requests under the UI daemon's own principal so that any caller passing `ui.filter` receives the full unredacted configuration regardless of their privilege level. No public exploit has been identified and this CVE is not in CISA KEV.
Log field injection in morgan, the Node.js HTTP request logger middleware, before version 1.12.1 allows unauthenticated remote attackers to manipulate parsed log records by embedding unescaped double quotes in HTTP headers such as User-Agent or Referer. The escapeLogField() function failed to escape the double-quote character, which serves as a field delimiter in the Apache combined log format that morgan emits by default, enabling a downstream log consumer that parses by field position to read attacker-supplied text as a subsequent field. In custom log formats that quote an attacker-controlled token before a server-controlled one, an attacker can forge field values including the HTTP response status code as seen by SIEMs, audit pipelines, or compliance tooling. No public exploit has been identified at time of analysis.
Denial of service in Apache ActiveMQ Artemis and Apache Artemis allows an authenticated client to exhaust shared broker thread resources by attaching a consumer with a crafted wildcard message selector that triggers excessive computational evaluation during message delivery. Affected versions span Apache ActiveMQ Artemis 1.0.0-2.44.0 and Apache Artemis 2.50.0-2.56.0, with a vendor-confirmed fix released in version 2.57.0 on September 9, 2026. No public exploit code or active exploitation has been identified at time of analysis.
Denial of service in Apache ActiveMQ Artemis and Apache Artemis message brokers allows authenticated clients holding MANAGE permission to crash broker processing threads by submitting crafted management-via-messaging requests that trigger unsafe Java deserialization. The deserializer processes method parameters the broker never actually uses, permitting gadget-chain payloads that consume excessive CPU and pin the thread pool. Both the legacy ActiveMQ Artemis lineage (1.3.0-2.44.0) and the newer Apache Artemis project (2.50.0-2.56.0) are affected; no public exploit or active exploitation has been identified at time of analysis.
Server-side request forgery in Apache Impala 2.0.0 through 4.5.1 allows SQL-authenticated users to coerce the Impala daemon into issuing arbitrary HTTP or file-system GET requests by specifying a malicious URL in the `avro.schema.url` table property. Internal service responses reachable by Impala but not directly by the attacker are partially exposed through SQL parsing error messages, enabling internal network reconnaissance, cloud metadata enumeration, and local file disclosure. Reported by zhaokaifei of ChinaTelecom, the vulnerability is resolved in version 4.5.2; no public exploit code or CISA KEV listing has been identified at time of analysis.
Stored cross-site scripting in Apache SkyWalking's Booster UI dashboard widget rendering (versions 10.2.0 through 10.4.0) allows an attacker with dashboard-edit access to inject persistent JavaScript that executes in the browser of any user viewing the affected dashboard. This is an incomplete remediation of CVE-2025-54057, meaning the original patch left residual unsanitized widget input paths. No public exploit code or active exploitation has been identified at time of analysis, though the prior CVE's public disclosure increases the likelihood of targeted research against the remaining surface.
Apache SkyWalking's PagerDuty alarm hook in versions 9.6.0 through 10.x transmits the PagerDuty integration routing key inside an unencrypted HTTP POST body before any redirect response from PagerDuty's HTTPS-only endpoint is received. Because the initial TCP socket write occurs in plaintext prior to the 301/302 redirect, a passive eavesdropper or MITM attacker positioned between the SkyWalking host and PagerDuty's API can capture the routing key verbatim from network traffic. No public exploit code has been identified and no active exploitation is confirmed; the practical impact is unauthorized PagerDuty event submission using the stolen credential, enabling false incident creation or alert fatigue rather than system compromise.
Stored cross-site scripting in Apache Allura allows authenticated repository contributors to inject persistent JavaScript payloads through code repository content, executing in the browsers of any user who subsequently views the affected forge pages. All releases through 1.20.0 of this open-source software forge platform are vulnerable. The Apache Security Team released version 1.21.0 in September 2026 to address this issue, as credited to researcher n0mi1k via the oss-security mailing list; no public exploit code has been identified at time of analysis.
Stored cross-site scripting via markdown HTML processing in Apache Allura through 1.20.0 permits an authenticated attacker to inject persistent malicious scripts that execute in the browsers of other users who view the compromised content - wikis, ticket comments, blog posts, or discussion threads. The vulnerability stems from insufficient sanitization of HTML embedded within markdown-rendered content across the forge platform's collaborative features. The Apache Software Foundation has released version 1.21.0 as the fix; no public exploit code or CISA KEV listing has been identified at time of analysis.
Control-character (newline) injection in Yoast SEO Premium before 27.6.1 allows an authenticated WordPress Author to write arbitrary Apache directives into the site's root .htaccess file via unsanitized redirect origins in file-based redirect mode. On Apache servers that process PHP directives, the injected auto_prepend_file directive can be chained with a polyglot image upload (available to Author-role users) to achieve full Remote Code Execution as the web server process. A public exploit is available via WPScan, making real-world exploitation feasible wherever the three required conditions align.
Stored XSS in the Apache Spark History Server (versions 3.0.0 through 3.5.7) allows a user with Spark job submission rights to inject unsanitized HTML/JavaScript into the History Server web UI via the application name field (spark.app.name), which executes in the browser of any higher-privileged user who subsequently views that job's history page. Apache rates this low severity due to layered prerequisites - the attacker must hold job submission rights and socially engineer an administrator into visiting the History Server. No public exploit has been identified at time of analysis; the vendor-released fix is Spark 3.5.8.
Unauthenticated network attackers can elicit Java stack traces from Red Hat IdM's Dogtag CA REST enrollment endpoint (POST /ca/rest/certrequests) by submitting malformed requests, causing HTTP 500 responses that expose internal implementation details under CWE-209. The same error path simultaneously amplifies the CA debug log with large multi-line stack traces, creating a log-fill resource exhaustion vector that drives disk growth and I/O contention on affected RHEL 6 through 10 deployments. No public exploit has been identified at time of analysis, but the attack requires no authentication and low complexity, making it accessible to unskilled opportunistic attackers targeting IdM infrastructure.
Cross-site scripting in Apache Wicket's AbstractSingleSelectChoice base class allows injection of unescaped HTML into the default/null option of DropDownChoice form elements. Affected versions span all supported Wicket branches from 8.0.0 through 10.10.0, as well as unsupported releases back to 1.5.0. An attacker who can influence the value returned by the overridden getNullValidDisplayValue() or getNullKeyDisplayValue() methods, or who controls the relevant resource bundle entries, can execute arbitrary JavaScript in a victim user's browser. No public exploit has been identified at time of analysis.
Cross-site scripting in Apache Wicket's Palette component allows injection of arbitrary HTML attributes into rendered `<option>` tags when applications override specific attribute-extension methods with attacker-influenced data. Affected are `wicket-extensions` versions spanning the 8.x, 9.x, and 10.x release lines; applications relying on the default method implementations are definitively not affected. Vendor-released patches are available at versions 8.19.0, 9.24.0, and 10.11.0; no public exploit code or CISA KEV listing has been identified at time of analysis.
Cross-site scripting in Apache Wicket's MetaDataHeaderItem class allows injection of arbitrary HTML attributes into generated <meta> and <link> header tags when applications pass attacker-influenced data to the addTagAttribute, forMetaTag, or forLinkTag APIs. The flawed escaping logic - replacing double-quote characters with backslash-double-quote, which carries no escaping semantics in HTML - permits a double-quote in an attacker-controlled value to break out of the attribute context and inject additional attributes such as JavaScript event handlers. Affected release lines span 8.0.0-8.18.0, 9.0.0-9.23.0, and 10.0.0-10.10.0; no public exploit has been identified at time of analysis.
Cross-site scripting in Apache Wicket's AutoLabelTextResolver allows injection of arbitrary markup into web pages when attacker-controlled data reaches a form component's label model via FormComponent#setLabel(IModel). The resolver, registered by default in every WebApplication, writes label values directly into rendered markup without any escaping and ignores the escape-model-strings application setting entirely - meaning there was no available configuration workaround. Applications are vulnerable wherever user-influenced data flows into a label model; this includes both stored XSS (data retrieved from a database) and reflected XSS (data sourced from the current request). No public exploit has been identified at time of analysis, but the vulnerability affects all supported release lines and all unsupported releases from 1.5.0 onwards.
Cross-site scripting in Apache Wicket's Button component allows injection of arbitrary markup into rendered pages when the button is bound to a `<button>` HTML element whose model contains attacker-influenced data. The root cause is an intentional design choice - Button's constructor clears the escape-model-strings flag to prevent double-encoding of `<input>` attribute values - that becomes a security flaw in the `<button>` rendering path, where element body content is never encoded by ComponentTag. Subclasses AjaxButton, AjaxFallbackButton, and WizardButton inherit the same constructor and are equally affected; no public exploit or CISA KEV listing is recorded at time of analysis.
Cross-site scripting vulnerabilities in Apache Wicket's AjaxEditableChoiceLabel and related wicket-extensions components allow an attacker who can influence rendered choice or model data to inject arbitrary HTML or JavaScript into page markup, executing in the browser of any user viewing the affected page. Versions 8.0.0 through 8.18.0, 9.0.0 through 9.23.0, and 10.0.0 through 10.10.0 of the org.apache.wicket:wicket-extensions module are confirmed affected. The root cause is that two distinct rendering paths bypass Wicket's default HTML escaping, and the escapeModelStrings configuration property has no corrective effect on these components. No public exploit has been identified at time of analysis.
Cross-site request forgery protection bypasses in Apache Wicket's ResourceIsolationRequestCycleListener allow network attackers to execute authenticated listener actions - link callbacks, form submits, behavior endpoints - on behalf of logged-in users across versions 9.1.0-9.23.0 and 10.0.0-10.10.0. The default FetchMetadataResourceIsolationPolicy incorrectly permits cross-site top-level GET navigations (exploitable because Wicket routes Link.onClick() and form callbacks through ordinary browser navigations) and unconditionally trusts Sec-Fetch-Site: same-site requests from sibling origins - both vectors deliver the victim's SameSite=Lax session cookie to the targeted listener. No public exploit has been identified at time of analysis; vendor-released patches are available in versions 9.24.0 and 10.11.0.
Path traversal in Apache Wicket's package resource URL handling exposes files outside the intended package directory to unauthenticated remote attackers, including files under WEB-INF that servlet containers ordinarily protect from direct access. Affected are all releases from 8.0.0 through 8.18.0, 9.0.0 through 9.23.0, and 10.0.0 through 10.10.0. Under default configuration the readable file set is bounded by the SecurePackageResourceGuard's extension allowlist (excluding .xml, .properties, .class), but all configurations unconditionally expose a path-existence oracle usable for reconnaissance, and applications using looser guard configurations can disclose web.xml and other sensitive configuration files. No public exploit identified at time of analysis.
Server-Side Request Forgery (SSRF) in Apache Shiro's Jakarta EE integration module (shiro-jakata-ee) enables a low-privileged authenticated user to steer server-initiated POST requests to an attacker-controlled host and transmit attacker-controlled data. Versions 2.0.0-alpha-0 through 3.0.0 of the shiro-jakata-ee artifact are affected, but only when the Jakarta EE integration module is deployed - the 1.x line and non-Jakarta-EE deployments are not vulnerable. No public exploit has been identified at time of analysis, and vendor-released patch 3.0.1 is available as of 2026-08-24.
Denial-of-service in Spring for Apache Kafka's `DeadLetterPublishingRecovererFactory` exposes consumer JVMs across all supported branches (2.8.x through 4.1.0) to crash or hang when processing messages with a crafted `retry_topic-original-timestamp` header. An authenticated Kafka producer can inject a ConsumerRecord carrying an oversized or malformed header byte array, which is passed without any length or format validation directly to Java's `BigInteger(byte[])` constructor, triggering heap memory exhaustion or an unhandled exception that disrupts message consumption. No public exploit code has been identified and the CVE does not appear in CISA KEV at time of analysis, but low attack complexity combined with broad version coverage makes this a credible availability threat for any Spring Kafka deployment using retry or dead-letter queue features.
Header type injection in Spring for Apache Kafka's default mapper configuration allows any Kafka producer with access to a consumed topic to inject java.net.InetAddress objects through the spring_json_header_types message header, triggering DNS resolution on the consumer host. All applications using @KafkaListener with the default JsonKafkaHeaderMapper or DefaultKafkaHeaderMapper - spanning versions 2.8.x through 4.1.0 - are affected without any non-default configuration required. No public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV.
Authorization bypass and privilege escalation in Apache APISIX 3.11.0-3.17.0 stem from the `attach-consumer-label` plugin failing to strip client-supplied consumer-label headers before using them in security decisions. An attacker who can reach the gateway can forge header values to impersonate a higher-privileged consumer label, bypassing route-level access controls. No vendor-released patch is available at time of analysis (fix version marked pending); no public exploit code or CISA KEV listing has been identified.
Insufficient session expiration in Apache Tomcat allows an authenticated attacker to maintain an active WebSocket connection after the underlying HTTP session has been invalidated, violating the Jakarta WebSocket specification's requirement that WebSocket sessions close when their parent HTTP session ends. Affected are all supported branches from 9.0.0.M1 through 9.0.120, 10.1.0-M1 through 10.1.57, and 11.0.0-M1 through 11.0.24, plus EOL branches 7.0.43-7.0.109 and 8.5.0-8.5.100. No public exploit or CISA KEV listing has been identified at time of analysis, and the low EPSS score (0.28%, 19th percentile) reflects limited real-world exploitation probability.
Unrestricted Solr query syntax passthrough in the TYPO3 EXT:solr enterprise search extension exposes indexed data to remote unauthenticated attackers via blind injection techniques. By crafting queries that exploit Solr's native field selectors, wildcards, and range operators, an attacker can enumerate schema field names and systematically extract stored values without triggering obvious errors. No public exploit code has been identified at time of analysis; the CVSS 4.0 score of 6.3 reflects high attack complexity (AC:H/AT:P) that limits opportunistic mass exploitation.
Unauthenticated REST API disclosure in Apache Allura through version 1.19.1 exposes certain content items to unauthorized actors without any credentials. The vulnerability stems from insufficient access control on REST endpoints, allowing any network-accessible client to retrieve content that should require authentication. No public exploit or CISA KEV listing has been identified at time of analysis, but the low exploitation barrier (unauthenticated, network-accessible) makes this a straightforward information leakage risk for any publicly exposed Allura instance.
Header injection via structured-mode CloudEvents in Apache Camel's Knative consumer enables unauthenticated SSRF, path traversal, and message-dispatch redirection against routes that forward to header-driven components. The flaw exists because CloudEvent extension fields in structured content mode (Content-Type: application/cloudevents+json) are copied directly into Camel Exchange headers without applying the KnativeHttpHeaderFilterStrategy that correctly guards the binary content-mode path - an incomplete fix of the same filter-bypass pattern addressed across multiple related CVEs (CVE-2025-27636, CVE-2025-29891, CVE-2025-30177, CVE-2026-40453, CVE-2026-47323). No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface - unauthenticated HTTP POST to a Knative endpoint - requires no special tooling.
Path traversal in Apache Camel's camel-azure-storage-datalake component allows anyone with write access to a consumed Azure Data Lake Storage Gen2 filesystem to direct the Camel process to write or overwrite files at arbitrary locations on the local filesystem. The downloadToFile operation constructs local paths by joining the configured fileDir with the remote file name exactly as returned by the Azure SDK - without lexical normalization or any boundary check - meaning a remote path name containing parent-directory segments (e.g., '../../etc/cron.d/payload') resolves outside fileDir. Depending on what the Camel process can write, this integrity violation can escalate to code execution or service disruption. No active exploitation has been identified at time of analysis, and vendor-released patches are available in versions 4.14.9, 4.18.4, and 4.22.0.
MIME header injection in Apache Camel's camel-mail MimeMultipart data format allows unauthenticated network senders to plant Camel-internal namespace headers onto the Camel Exchange when headersInline is set to true, potentially redirecting what downstream route components - such as camel-sql - execute. Versions 2.17.0 through 4.14.8, 4.15.0 through 4.18.3, and 4.19.0 through 4.21.x are affected across all release lines until the current fixes. No public exploit code or active exploitation has been identified; EPSS sits at 0.16% and SSVC rates exploitation status as none, making this a patch-priority rather than emergency-response item for most organizations.
Heap exhaustion via unbounded memory leak in micrometer-core affects Java applications using Apache HttpAsyncClient (4.x or 5.x) instrumented with MicrometerHttpClientInterceptor. When asynchronous HTTP requests fail before receiving any server response - due to connection resets, network timeouts, or unreachable endpoints - the per-request tracking state allocated by the interceptor is never released, accumulating indefinitely on the JVM heap. Sustained failure conditions (such as a misbehaving or attacker-controlled upstream server) can drive heap exhaustion to OutOfMemoryError, crashing the instrumented application. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Session cookie forgery in Apache::AppSamurai::Util through version 1.01 is possible because CreateSessionAuthKey derives its entire entropy from observable runtime state - wall-clock microseconds and the Apache worker process ID - rather than a cryptographically secure random source. An unauthenticated remote attacker who can bound the second in which a target session was created and enumerate the small PID space can construct candidate 64-character hex cookies and recover a valid session token through online brute-force, bypassing authentication for all resources protected by the module. No public exploit code has been identified and SSVC confirms no current exploitation, though the attack is mechanically feasible given the constrained key space.
Resource exhaustion in Apache CloudStack's scoped global configuration subsystem-spanning versions 4.7.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0-allows authenticated low-privilege users to gradually trigger a denial-of-service condition against the management server. The vulnerability (CWE-772) affects multiple plugins including Quota and Host-HA, which allocate resources during configuration operations but fail to release them after their effective lifetime. No public exploit or active exploitation has been identified; vendor-released fixes are available in 4.20.3.1 and 4.22.1.1.
Improper output encoding in Apache CloudStack's management UI exposes administrators to cross-site scripting (XSS) when using the Lock User functionality across versions 4.20.0.0-4.20.3.0 and 4.21.0.0-4.22.1.0. A low-privilege user can embed a malicious script payload in a user-controlled field; when an administrator invokes the Lock User workflow, the CloudStack UI renders the payload without proper HTML or JavaScript escaping, executing it in the admin's browser session. No public exploit or CISA KEV listing has been identified at time of analysis, but the potential for admin session hijacking makes this a meaningful risk in multi-tenant environments.
Pre-validation SSRF in Apache CloudStack's template and ISO registration allows authenticated users to trigger HTTP HEAD/GET requests to arbitrary URLs - including internal network resources - before URL validation is applied. Affected versions are 4.20.3.0 and 4.21.0.0 through 4.22.1.0; vendor-released patches exist in 4.20.3.1 and 4.22.1.1. No public exploit code or active exploitation has been identified at time of analysis, and exploitation requires valid CloudStack credentials with template-registration privileges.
Sensitive information exposure in Apache CloudStack's Webhook module allows unauthorized actors to view data they should not have access to during webhook delivery listing and deletion operations. Affected deployments span versions 4.20.0.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0, covering two active release trains. No public exploit or active exploitation has been identified at time of analysis; vendor-released patches are available.
Missing authorization in Apache CloudStack's listHostTags API allows domain administrators to enumerate host tags across all domains in a multi-tenant deployment, violating tenant isolation boundaries established by the domain hierarchy. Affected versions span 4.12.0.0 through 4.22.1.0 across two release trains, with vendor-released patches in 4.20.3.1 and 4.22.1.1 confirmed by the Apache security advisory. No public exploit code exists and the vulnerability is not listed in CISA KEV, but the risk is meaningful in shared, multi-tenant CloudStack environments where cross-domain host tag visibility undermines infrastructure confidentiality guarantees between tenants.
Improper access control in Apache CloudStack's annotation APIs (addAnnotation and listAnnotation) allows any authenticated user to read and write annotations on entities they do not own. The APIs perform an ownership check when an entity UUID is supplied but fail to enforce the result of that check, reducing authorization to a formality that any authenticated user can bypass. No public exploit has been identified at time of analysis; no EPSS or CISA KEV data is available, but the bug affects all CloudStack deployments from 4.15.0.0 onward until the patched releases.
Server-Side Request Forgery in Apache InLong Manager (versions 2.0.0-2.3.x) allows any authenticated user - no administrative role required - to coerce the Manager service into issuing outbound HTTP requests or TCP connections to arbitrary internal hosts and ports. This effectively turns the InLong Manager into an open proxy for internal network reconnaissance, enabling access to otherwise firewalled services such as cloud instance metadata endpoints, internal APIs, or database management interfaces. No public exploit has been identified at time of analysis, but the low privilege bar makes this broadly reachable within any deployment that permits shared user access.
Uncontrolled Resource Consumption (CWE-400) in Apache InLong versions 2.0.0 through 2.3.x exposes two related attack surfaces: authenticated users can trigger excessive resource consumption to degrade service availability, and the same pathway permits upload of non-official packages, introducing a package-integrity risk alongside the denial-of-service vector. Affected deployments running any release in the 2.0.0-2.3.x range should treat this as a priority upgrade given the dual nature of the flaw. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Unauthorized template information disclosure in Apache InLong 2.0.0 through 2.3.x allows authenticated users who are not designated template responsible persons to view template configurations they should not have access to. The CVE is tagged CWE-400 (Uncontrolled Resource Consumption) and classified as Denial of Service, yet the description describes an access control bypass - this is a data contradiction that analysts should flag before making control decisions. No public exploit or active exploitation has been identified. Vendor fix is available in Apache InLong 2.4.0.
Cross-request data leakage in Apache Struts 7.2.1's JSON plugin allows an authenticated remote attacker to observe response content associated with a concurrent request belonging to a different user. The root cause is a thread-safety defect (CWE-567) in the SMD/JSON-RPC interceptor, where per-response serialization state is not isolated between concurrent requests. Exploitation is constrained to the non-default SMD/JSON-RPC mode of the JSON interceptor; no public exploit code has been identified at time of analysis, and the EPSS score of 0.15% (4th percentile) reflects the limited realistic exploitation surface.
Cross-request data exposure in the Apache Struts JSON plugin (version 7.2.1) results from per-request parsing state being improperly shared across concurrent requests, enabling information observable in one user's session to leak into another's. Authenticated remote attackers targeting applications that have explicitly enabled JSON action population can exploit this concurrency flaw (CWE-567) to read partial request data or circumvent configured parsing limits. With an EPSS of 0.15% (4th percentile), no CISA KEV listing, and no public exploit identified at time of analysis, real-world risk is low and narrowed further by the non-default plugin requirement.
Cross-site scripting in Apache Allura's Markdown rendering (versions 1.10.0 up to but not including 1.19.1) allows an attacker to inject script-related HTML into content that other users view, executing arbitrary JavaScript in their browsers. Because Allura is a collaborative forge where users routinely post Markdown in tickets, wiki pages, and comments, the payload is most likely stored and delivered to victims who open the affected page. No public exploit identified at time of analysis, and there is no CISA KEV listing or POC signal; the Apache PMC has released version 1.19.1 as the fix.
Cross-site scripting (XSS) in Apache Allura's code-display feature allows an attacker who can place crafted content into a rendered code view to execute arbitrary JavaScript in the browser of any user who views that code, in all versions before 1.19.1. Because Allura is forge/project-hosting software, a successful attack can hijack the sessions of project members or administrators. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Insecure Direct Object Reference (IDOR) in Apache Allura before 1.19.1 allows unauthorized access to multiple Artifact types due to missing server-side permission checks. Attackers who can interact with the platform can reference artifact objects directly by their identifiers and retrieve content beyond their authorization level, resulting in information disclosure across potentially broad artifact categories. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Secret exposure in Apache Airflow's Rendered Templates UI allows any authenticated user with task-level view access to read plaintext credential values that should have been masked. The secrets masker's `isinstance(str)` guard silently skips dict-typed Python objects, meaning JSON Variables accessed via `var.json` and containing dict payloads (e.g., database credentials, API keys stored as structured JSON) are rendered in cleartext rather than redacted. No public exploit is identified at time of analysis; however, the disclosure requires nothing more than standard UI navigation by a legitimately authenticated user.
Unsafe deserialization in Apache Airflow's XCom REST API allows an authenticated user with XCom write-and-read access to instantiate arbitrary `airflow.*` classes on the API server by smuggling reserved serialization keys inside JSON string literals. The `_check_forbidden_xcom_keys` guard inspected `dict`, `list`, and `tuple` types but did not attempt to JSON-decode `str` values, so a payload like `json.dumps({"__classname__": "airflow.sdk.definitions.connection.Connection"})` passed the write-time check and was later reconstructed into a live Python object when read back via `?deserialize=true`. No public exploit has been identified at time of analysis; vendor-released patch is available in apache-airflow 3.3.1.
Sensitive values stored as deeply nested lists, tuples, or sets in Apache Airflow Variables are displayed unmasked in the Variables UI due to a recursion-depth logic error in the secrets masker. This is an incomplete-fix follow-up to CVE-2026-42358: that prior fix made dictionary traversal unbounded but left list/tuple/set structures subject to the depth cutoff, allowing values beyond that depth to appear in plaintext on screen. The practical impact is narrow - any authenticated user who can see the Variable in the UI already has read access to the full value through the Variables REST API - making this a shoulder-surfing defense gap rather than an access-control bypass. No public exploit has been identified at time of analysis.
Sensitive credential exposure in Apache Airflow 3.3.0 allows an authenticated Viewer with configuration-read access to retrieve team-scoped sensitive options - including Celery broker URLs with embedded credentials - in cleartext via the Config API. The secrets masker evaluated sensitivity against raw section names without resolving team-prefixed sections (e.g., [team_a=celery]) back to their registered base section, so team-scoped overrides silently bypassed masking while equivalent global options were correctly redacted. This is a third distinct masker bypass variant following CVE-2026-48828 and CVE-2026-48892, meaning deployments that already upgraded to 3.3.0 to remediate those issues remain exposed. No public exploit identified at time of analysis.
Cleartext secret exposure in Apache Airflow's audit log affects all versions before 3.3.1, allowing any authenticated user with audit-log read access to recover Variable values and Connection `extra` credentials verbatim - without holding Variables or Connections read permissions. The bulk API endpoints (`PATCH /api/v2/variables`, `PATCH /api/v2/connections`) bypassed audit-log masking because the masker inspected only top-level request fields while bulk payloads nest entities two levels deep under `actions[].entities[]`. The Airflow UI's Import Variables action posts to this same bulk endpoint, meaning a routine operator import silently writes every secret in the uploaded file to the unmasked audit log. No public exploit is identified at time of analysis, but the vulnerability is fully exploitable by any authenticated user with log access, and deployments that upgraded to 3.3.0 in response to the related CVE-2026-50204 remain vulnerable and must upgrade again.
Cleartext exposure of list-shaped Variable secrets in Apache Airflow Task SDK (all versions before 3.3.1) allows any authenticated Airflow user to recover sensitive values directly from task execution logs and the Rendered Templates UI. The masking logic in _mask_and_deserialize_variable correctly handled string- and dict-typed JSON Variable values but contained no branch for the list type, so arrays - which may hold passwords, API tokens, or connection strings - were returned unredacted. No public exploit has been identified at time of analysis; however, organizations that patched CVE-2026-59244 remain fully exposed because that fix addressed only the dict case, and must upgrade again to 3.3.1.
Cross-team DAG authorization bypass in Apache Airflow versions prior to 3.3.1 allows authenticated users in one team to trigger DAG runs and read XCom values belonging to other teams. The asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom check in wait_dag_run_until_finished both passed DagDetails without resolving the DAG's team_name, causing team-aware auth managers (e.g., Keycloak) to evaluate the permission against the global DAG resource instead of the team-scoped DAG:<team> resource. This is a missing authorization flaw (CWE-862) affecting only deployments running multi-team mode with a team-aware auth manager; FAB auth manager deployments are explicitly unaffected. No public exploit code or CISA KEV listing has been identified at time of analysis.
Cross-team credential access in Apache Airflow before 3.3.1 allows authenticated members of one team to invoke another team's Connection credentials through the POST /api/v2/connections/test API endpoint, exploiting a broken namespace-isolation guard in the environment-variable secrets backend. The flaw-confirmed by Apache with patches in PRs #70736 and #70902-combines a guard that only triggered on unscoped (global) requests with a regex incapable of matching team names containing underscores, even though underscores are explicitly permitted in Airflow team name validation. Exploitation requires a precise configuration alignment of multi_team mode, an explicitly enabled test_connection endpoint, and environment-variable-provisioned team secrets; no public exploit has been identified at time of analysis.
Cross-team credential disclosure in the Apache Airflow Google Provider's Cloud Secret Manager backend exposes every team's Connections and Variables to every other team in multi-team deployments. The backend's public methods accepted a team_name parameter but silently discarded it before the internal secret lookup, collapsing all team namespaces into one shared, unscoped lookup. No public exploit has been identified at time of analysis; the vendor-released fix is apache-airflow-providers-google 22.3.0.
Cross-team secret disclosure in Apache Airflow Amazon Provider (all versions before 9.34.0) allows an authenticated Airflow team member to read Connections, Variables, or Configuration secrets belonging to a different team in a multi-team deployment. By crafting a lookup ID that embeds the '--' team namespace separator, an attacker causes the provider's team-scoped lookup to miss and the pre-patch team-agnostic fallback to resolve the target team's AWS Secrets Manager or SSM Parameter Store secret in plaintext. No public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV, but the exploit technique is mechanically straightforward given the documented '--' naming convention.
Cross-team secret disclosure in Apache Airflow's Yandex Lockbox secrets backend exposes one team's credentials to members of a different team in multi-team deployments. Any authenticated Airflow user belonging to any team can retrieve connections or variables owned by another team by supplying a secret ID that embeds the target team's namespace separator sequence. The flaw requires only that multi-team mode and the Yandex Lockbox backend are active - both standard, documented configurations - and yields full plaintext credential exposure. No public exploit or CISA KEV listing exists at time of analysis.
Cross-team credential disclosure in the Apache Airflow Microsoft Azure provider's Key Vault secrets backend allows any authenticated team member to read credentials belonging to a different team in multi-team deployments running versions prior to 14.1.0. The backend's team-scoped lookup falls through to a team-agnostic resolution when the scoped lookup misses, and an attacker in one team can deliberately trigger this by supplying a connection or variable ID whose normalized form encodes the target team's namespace prefix. No public exploit has been identified at time of analysis, but the attack primitive is directly derivable from the published patch diff, making this a credible insider-privilege escalation risk for any organization using this backend in multi-team mode.
JWT tokens written to Apache Ranger logs in versions 2.8.0 and earlier remain replayable, allowing any party with read access to those logs to authenticate as legitimate users without knowing their credentials. The flaw (CWE-532) is particularly severe because Ranger controls data security policies across Hadoop ecosystems - impersonating a Ranger user can yield control over access policies for HDFS, Hive, HBase, and related services. No public exploit or CISA KEV listing exists at time of analysis; Apache has confirmed a fix in version 2.9.0.
Traefik's BasicAuth middleware in versions 3.6.11-3.6.24 and 3.7.0-3.7.9 permits an authenticated low-privilege user to forge arbitrary backend identities via a singleflight key collision race condition. By concatenating their known valid password with a retrieved stored bcrypt hash, an attacker crafts a singleflight deduplication key identical to a legitimate in-flight request's key; the middleware returns the legitimate request's successful authentication result to the attacker's request, then propagates the attacker's chosen unconfigured username to the backend as a trusted identity. A fully working proof-of-concept achieving 25-of-25 successful identity forgeries under default bcrypt cost is publicly available in the GitHub security advisory; no CISA KEV listing has been identified at time of analysis.
Apache Polaris incorrectly enforces storage location boundaries during Iceberg table and view registration, enabling an authenticated principal with registration privileges to cause the catalog service to read S3 objects outside the configured allowed storage perimeter. Exploitation depends on a deployment running S3 credential vending where the catalog's underlying credentials can access objects beyond the allowed boundary - a constrained but realistic enterprise configuration. The demonstrated impact is limited to partial confidentiality disclosure of out-of-bounds objects; no unauthorized write or availability impact has been demonstrated, and no public exploit or active exploitation has been identified at time of analysis.
Improper authorization in Apache Answer through version 2.0.1 allows any authenticated user to reject arbitrary pending edit-revisions without holding review permissions. The missing authorization check on the reject operation means content moderation controls are effectively bypassed by ordinary users, enabling disruption of the peer-review workflow. No public exploit code exists and this vulnerability is not listed in the CISA KEV catalog at time of analysis.