Apache
Monthly
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.
Remote code and command injection in Apache Allura before 1.19.1 lets unauthenticated attackers smuggle attacker-controlled arguments into git command invocations through specially crafted inputs. Because Allura is a project-hosting and forge platform that shells out to git, this argument injection (CWE-88) can be leveraged to influence git behavior and, depending on the invoked subcommand, achieve command execution against the hosting server; no public exploit has been identified at time of analysis and EPSS exploitation probability is low (0.18%).
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 3.0.0 through 3.3.0 allows any DAG author to achieve arbitrary code execution in the Scheduler and API server by placing a crafted value in an operator's executor_config field. The serialization layer reconstructed exception nodes by calling import_string() on an attacker-controlled class name with no allowlist, enabling import and invocation of arbitrary callables such as subprocess.check_output or builtins.eval. Both affected components hold the metadata database credentials and JWT signing secret, making full infrastructure compromise a realistic outcome. No public exploit has been identified at time of analysis, but no non-default configuration is required. This is a distinct sink from CVE-2026-33264, meaning deployments that already patched that earlier advisory remain fully vulnerable and must upgrade again to apache-airflow 3.3.1.
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.
Remote code execution and scheduler-process disruption in Apache Airflow 3.3.0 stems from unguarded deserialization of task instance `next_kwargs` during the scheduler's unconditional `awaiting_input` sweep, a code path introduced as part of the 3.3.0 human-in-the-loop task rewrite. Any authenticated DAG author who can influence task state through the task execution API can supply a crafted payload that causes arbitrary module import and object instantiation inside the scheduler process, or terminate the scheduler job entirely. No public exploit has been identified at time of analysis, but a vendor-released patch exists in 3.3.1; deployments that previously patched CVE-2026-58076 are still vulnerable through this distinct code path and must upgrade.
Unsafe deserialization in Apache Airflow 3.3.0's Task SDK allows an authenticated DAG author to cause arbitrary module imports inside the scheduler process. By controlling a task instance's `next_kwargs` via the task execution API, an attacker can inject a crafted callback path that the scheduler's unconditional `awaiting_input` timeout sweep deserializes by re-running the `SyncCallback` constructor - triggering an import of the named module in the scheduler's process space. Because `SyncCallback` is itself an Airflow class, it bypasses the `allowed_deserialization_classes` allow-list, making tightening that setting ineffective. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS score of 8.8 reflects the severity of the potential scheduler process compromise.
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.
Authorization bypass in Apache Airflow's Backfill API (all versions prior to 3.3.1) allows any authenticated user holding edit permission on a single DAG to read, pause, cancel, and fail backfills belonging to any other DAG. The flaw is a type-parsing mismatch in FastAPI's dependency resolution layer: the authorization dependency parsed the `backfill_id` path parameter with Python's `int()` while the route handler declared `NonNegativeInt` via Pydantic, which in lax mode coerces inputs like `'42.0'` that `int()` rejects-causing the two components to authorize and act on different DAGs. Backfill IDs are sequential, making cross-DAG enumeration trivial; no public exploit code has been identified at time of analysis, though the technique is directly reproducible from the published patch diff.
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.
Server-impersonation via broken TLS hostname verification affects Apache HttpComponents Client 5.4 through 5.6.3 when applications use the asynchronous HttpClient, where the HostnameVerificationPolicy#BUILTIN setting is silently ignored. An adversary positioned to intercept and modify network traffic can present a valid certificate issued for an unrelated domain and the async client will accept it, defeating the core TLS server-identity check and exposing transmitted data. There is no public exploit identified at time of analysis and EPSS is very low (0.09%), but the CVSS base score is 9.1 and the classic (synchronous) HttpClient is explicitly unaffected.
Unauthenticated credential theft in the InstaWP Connect WordPress migration plugin (all versions ≤ 0.1.3.6) exposes database access details and API signatures on Apache servers during active migration windows. The plugin predictably derives its AES-256-CBC decryption passphrase as SHA256(migrate_key), where the migrate_key is directly leaked in the filename of the unprotected options file via Apache directory listing - allowing an attacker who finds the file to mathematically recover the encryption key and decrypt the options payload without any brute force. Recovery of the api_signature may enable downstream remote code execution via InstaWP's service API. No public exploit or CISA KEV listing has been confirmed at time of analysis, though the deterministic key derivation significantly reduces exploitation effort.
Server-Side Request Forgery in Apache Allura before 1.19.1 lets attackers abuse the project webhook feature to coerce the server into issuing arbitrary outbound HTTP requests, exposing internal services and cloud metadata endpoints. The flaw carries a CVSS 9.1 and is fixed in 1.19.1; it was disclosed via the Apache security team and oss-security on 2026-08-11. There is no public exploit identified at time of analysis and EPSS is low (0.20%, 11th percentile), indicating no observed weaponization yet.
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.
Unauthenticated classpath asset disclosure in Apache Tapestry 5.5.0 through 5.9.0 exposes arbitrary files on the Java classpath to remote attackers via specially crafted HTTP URLs. The tapestry-core component fails to restrict URL-based access to classpath resources, meaning attackers can retrieve sensitive files such as configuration files, properties files containing credentials, and compiled .class files. No public exploit code has been identified at time of analysis, but the attack requires no authentication, no user interaction, and minimal complexity - lowering the bar for exploitation significantly.
Command injection in Apache Ranger versions 0.6 through 2.8 allows attackers to inject and execute operating-system commands through improperly neutralized special elements (CWE-77), yielding full compromise of the host running the Ranger service. The NVD CVSS vector scores it 9.8 (network, low complexity, no privileges, no user interaction) with high confidentiality, integrity, and availability impact, meaning a successful exploit can read, alter, and destroy data on the affected component. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV; EPSS estimates a 1.01% 30-day exploitation probability (60th percentile).
SQL injection in Apache Ranger allows remote attackers to inject arbitrary SQL through the application's data-access layer, exposing the backing policy/audit database to full read, modification, and destruction. Because Ranger is the centralized authorization and access-control service for Hadoop and related big-data platforms, compromise here can undermine security policy enforcement across an entire data estate. Rated CVSS 9.8; no public exploit identified at time of analysis, EPSS is low (0.21%, 12th percentile), and the flaw is fixed in version 2.9.0.
Privilege escalation in Apache Ranger versions 2.8.0 and earlier allows an attacker to elevate their effective permissions by manipulating a URL parameter, undermining the very access-control layer Ranger is meant to enforce across Hadoop-ecosystem services. Apache rates it CVSS 9.8 with a network, low-complexity, no-privilege vector, though the 'privilege escalation' framing implies a pre-existing foothold that is worth verifying. There is no public exploit identified at time of analysis, and the EPSS score is low (0.19%, 9th percentile), indicating no observed mass-exploitation activity yet.
Remote code execution in Apache Ranger versions up to and including 2.8.0 arises from JDBC URL injection (CWE-94), letting an attacker who can influence a database connection string coerce the server into loading attacker-controlled JDBC driver behavior and executing arbitrary code on the Ranger host. This flaw affects the centralized authorization framework used to govern access across Hadoop-ecosystem services, so compromise undermines the very control plane meant to enforce data security. There is no public exploit identified at time of analysis and EPSS is low (0.36%, 29th percentile), but the fix in 2.9.0 and the critical 9.8 CVSS warrant prompt patching.
Remote code execution in Apache Ranger 2.8.0 and earlier arises from arbitrary Java class instantiation in the plugin-schema-registry component, letting an attacker who can reach the affected interface load and run attacker-controlled classes and achieve full compromise (CWE-94). The flaw carries a critical CVSS 9.8 and is fixed in Ranger 2.9.0. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, with EPSS at a modest 0.58% (45th percentile).
Remote code execution in Apache Ranger versions up to and including 2.8.0 stems from unsafe script evaluation in the GraalScriptEngineCreator component, letting an attacker inject and execute arbitrary code (CWE-94) on the Ranger host. Because Ranger is the central authorization and data-governance layer for Hadoop-ecosystem services, compromise can undermine access control across an entire big-data platform. There is no public exploit identified at time of analysis, it is not on CISA KEV, and EPSS is modest (0.34%, 26th percentile), but the 9.8 CVSS rating reflects the potential for full host compromise once conditions are met.
Unauthenticated access to Apache Ranger Download APIs on versions 2.8.0 and earlier exposes sensitive authorization policy data to any remote attacker with network connectivity. The missing authentication check (CWE-306) means no credentials or privileges are required to invoke these endpoints and retrieve their output. No public exploit code has been identified at time of analysis, but the low complexity and zero-authentication nature of the CVSS vector (AV:N/AC:L/PR:N/UI:N) makes this trivially exploitable by any attacker who can reach the Ranger Admin interface.
TLS hostname verification failure in Apache Ranger Client Code allows network-positioned attackers to intercept sensitive traffic via man-in-the-middle attacks against all deployments running version 2.8.0 or earlier. The client fails to validate that a server's TLS certificate hostname matches the actual server being contacted (CWE-297), meaning a forged or mismatched certificate will be accepted silently. A vendor-released patch is available in version 2.9.0; no public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
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.
Brute-force credential attacks against Apache Ranger's UnixAuth component are possible in all versions up to and including 2.8.0, because the authentication endpoint imposes no rate limiting, account lockout, or anti-automation controls (CWE-307). Any deployment that has explicitly configured UnixAuth - a configuration the vendor labels as not recommended for production - exposes its Ranger admin interface to automated password-guessing from unauthenticated network attackers. No active exploitation is recorded in CISA KEV and no public POC has been identified at time of analysis, but the unauthenticated network vector (AV:N/PR:N/AC:L) makes automated credential attacks trivially executable against any network-reachable instance.
Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the database by sending a single crafted malformed frame. Improper validation of length fields (CWE-789) causes IoTDB to attempt arbitrarily large heap allocations, exhausting JVM memory and terminating the process with an OutOfMemoryError. Versions before 1.3.8 on the 1.x branch and 2.0.0 through 2.0.8 on the 2.0.x branch are affected; no public exploit code or CISA KEV listing has been identified at time of analysis.
Denial of service in the Go implementation of Apache Fory allows unauthenticated remote attackers to crash affected services by sending crafted serialized data containing malformed type metadata, triggering an uncaught Go runtime panic. Affected versions span 0.16.0 through 1.5.0 (exclusive), while all non-Go language implementations remain unaffected. No public exploit code or active exploitation (CISA KEV) has been identified; the EPSS score of 0.18% (8th percentile) corroborates low current exploitation activity despite the high CVSS base score.
Heap type confusion in the Apache Fory C++ deserialization engine (versions 0.14.0 up to but not including 1.5.0) lets a crafted payload bypass type-compatibility checks during polymorphic smart-pointer deserialization, so an object of an incompatible type is handled as its declared base type. Because CWE-502 untrusted-data handling here corrupts memory rather than merely mis-parsing values, an attacker who controls serialized input can trigger undefined behavior ranging from denial of service to arbitrary code execution. This is rated CVSS 9.8 and is fixed in 1.5.0; there is no public exploit identified at time of analysis and EPSS is low at 0.21%.
Out-of-bounds heap read in Apache Fory C++ versions 0.14.0 through 1.4.x allows attackers supplying crafted deserialization payloads to trigger information disclosure or denial of service. The flaw resides specifically in the tagged integer fast-path deserializer and only manifests when the application processes structs with tagged integer fields. No public exploit or active exploitation has been identified at time of analysis, and a vendor-released patch is available in version 1.5.0.
Command injection in sysPass's backup service allows any authenticated administrator to execute arbitrary OS commands as the web server process user by storing shell metacharacters in the backup path configuration setting and triggering a backup operation. Because sysPass is a self-hosted password manager, successful exploitation grants direct read access to the master encryption key and entire credential vault, enabling mass credential disclosure and lateral movement to every system whose passwords are stored in sysPass. A public proof-of-concept is available via the referenced gist (https://gist.github.com/W40X/6747ba1b7da7bb69b0c0e162628df279); no CISA KEV listing was identified at time of analysis.
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.
Cross-user HTTP response poisoning in Traefik's default reverse proxy allows an unauthenticated remote attacker using HTTP/2 or HTTP/3 to smuggle responses into other clients' backend connections, potentially delivering authenticated or private content from one user to another. All supported Traefik branches through v2.11.52, v3.6.23, and v3.7.8 are affected in default configuration when fronting Go net/http or gunicorn/Flask backends, which are confirmed 'armed' (respond to CONNECT with keep-alive non-2xx without draining the body). A proof-of-concept is publicly available demonstrating reliable cross-user poisoning including a cascade scenario where 8 of 8 sequential victims read responses that were not their own; no CISA KEV listing was present at time of analysis.
SQL injection in the Apache Portable Runtime Utility (APR-util) affects the apr_dbd_oracle database provider in versions 1.6.0 through 1.6.3, letting remote attackers inject arbitrary SQL through an application that relies on this DBD backend for query construction or escaping. Rated CVSS 9.1 with high confidentiality and integrity impact but no availability impact, it allows unauthorized reading and modification of Oracle-backed data. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Heap-based buffer overflow in Apache Portable Runtime Utility's redis client component allows remote unauthenticated attackers to crash applications that use the library, resulting in a denial of service. Affected versions span APR-util 1.6.0 through 1.6.3; version 1.6.4 resolves the issue per Apache's advisory on the oss-security mailing list. No public exploit code and no CISA KEV listing have been identified at time of analysis, though SSVC classifies the flaw as automatable with partial technical impact, indicating it could be scripted for broad scanning.
Heap-based buffer overflow in Apache Portable Runtime Utility's memcached client component (versions 1.3.0 through 1.6.3) allows remote unauthenticated attackers to crash affected applications, causing denial of service. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms full availability impact with no confidentiality or integrity exposure. No public exploit identified at time of analysis, but SSVC marks this as automatable, meaning scripted mass scanning is feasible once attack primitives are established.
Authorization scope escalation in Apache CXF's OAuth2 Dynamic Client Registration endpoint allows any registering client to self-assign privileged scopes by supplying arbitrary `scope` values in the registration request, which the authorization server stores verbatim without validating against a server-defined allowlist. Affected versions span the 3.x, 4.1.x, and 4.2.x release lines; patched releases 3.6.12, 4.1.8, and 4.2.3 are available per the Apache advisory. No public exploit or active exploitation has been identified at time of analysis, but the straightforward exploitation path - crafting a single registration request - makes this a meaningful authorization bypass risk for any deployment exposing CXF's OAuth2 AS with Dynamic Client Registration enabled.
Apache CXF's JwtRequestCodeFilter blindly copies all claims from a validly-signed JWT request object into the OAuth2 authorization parameter map, including security-sensitive fields that must not be client-controlled: code_challenge, code_challenge_method, nonce, and state. Affected are all Apache CXF deployments using this filter for OAuth2/OIDC authorization code flows prior to versions 4.2.3, 4.1.8, and 3.6.12. An OAuth2 client with a known or compromised client_secret can craft a signed request JWT that overrides the PKCE parameters established in the outer HTTP request, effectively nullifying PKCE authorization code binding and OIDC replay protection. No public exploit code or CISA KEV listing has been identified at time of analysis.
Authentication bypass in Apache CXF's OIDC relying-party implementation allows network-accessible attackers to forge self-issued ID tokens that skip all required OpenID Connect claim checks - issuer, subject, audience, time bounds, and sub_jwk binding - effectively impersonating any user identity. Affected are all Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 when the relying party is explicitly configured to accept self-issued OIDC tokens, a non-default setting. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface is constrained to a narrow set of deliberately misconfigured deployments.
Apache CXF's DefaultEncryptingCodeDataProvider allows captured OAuth 2.0 authorization codes to be redeemed an unlimited number of times, violating RFC 6749's single-use requirement. The removeCodeGrant() method that should invalidate a code after first exchange fails to do so, meaning any attacker who intercepts or obtains a legitimate authorization code can replay it repeatedly to obtain additional access tokens. No public exploit has been identified at time of analysis, and the issue is addressed in patched releases 4.2.3, 4.1.8, and 3.6.12.
Token revocation bypass in Apache CXF's DefaultEncryptingOAuthDataProvider allows revoked OAuth access and refresh tokens to remain functionally valid indefinitely - the provider continues to decrypt them successfully and TokenIntrospectionService returns active:true in direct violation of RFC 7009 and RFC 7662 mandates. All Apache CXF deployments using this built-in OAuth data provider and relying on token revocation as a security control are affected across the 3.6.x, 4.1.x, and 4.2.x branches. An attacker or suspended user who retains a revoked token can continue accessing protected resources as though revocation never occurred, bypassing intended authorization boundaries. No public exploit has been identified at time of analysis, though the attack requires no tooling beyond a standard HTTP client.
XML External Entity injection in Apache CXF's WSDL import processing allows attackers who can influence imported WSDL or XSD documents to bypass XXE protections applied to the top-level WSDL. CXF correctly hardens top-level WSDL parsing via StaxUtils, but delegates all <wsdl:import> and <xsd:import> resolution to WSDL4J, which lacks equivalent DOCTYPE and external entity restrictions - creating a security boundary mismatch that nullifies the top-level protections. No public exploit has been identified at time of analysis, but CWE-611 is a well-understood attack class with established tooling; successful exploitation against vulnerable deployments can yield arbitrary server-side file reads and SSRF. Vendor-released patches are available across three active release branches.
Authorization Code Substitution in Apache CXF's OpenID Connect Relying Party implementation allows remote attackers to hijack authenticated sessions when CXF is deployed in Hybrid Flow mode with a non-compliant or misconfigured Identity Provider that omits the c_hash parameter. Successful exploitation yields full authenticated access equivalent to account takeover, with high confidentiality and integrity impact. No public exploit has been identified at time of analysis, but SSVC classifies the attack as automatable with total technical impact once the prerequisite IdP condition is present.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
Denial of service persists in Apache CXF due to an incomplete remediation of CVE-2026-50645, allowing unauthenticated network attackers to exhaust server resources by submitting messages containing an excessive number of MIME attachment headers. All Apache CXF deployments running versions prior to 4.2.3, 4.1.8, or 3.6.12 remain vulnerable despite having applied the prior patch. No public exploit code or active exploitation has been identified at time of analysis, but the bypass-of-fix nature of this vulnerability means any organization that patched CVE-2026-50645 and considered itself remediated must re-patch.
Uncontrolled resource consumption in Apache CXF's JAX-RS form parameter processing enables remote denial-of-service attacks against any exposed endpoint accepting form-encoded requests. The framework provides a 'maxFormParameterCount' configuration knob but sets no default ceiling, meaning unpatched deployments will parse arbitrarily large parameter sets until memory or CPU is exhausted. Fixed versions (4.2.3, 4.1.8, and 3.6.12) enforce a default cap of 500 parameters; no public exploit or CISA KEV listing has been identified at time of analysis.
Unbounded attachment ingestion in Apache CXF enables remote denial-of-service against any endpoint that processes multipart messages. Versions prior to 4.2.3, 4.1.8, and 3.6.12 imposed no default ceiling on the 'attachment-max-size' parameter, allowing attackers to exhaust server memory or processing capacity by submitting arbitrarily large attachments. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the low attack complexity makes this a realistic threat for internet-exposed CXF deployments.
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.
Privileged API access in Apache Answer through 2.0.1 persists after an administrator loses their authority: keys issued to an admin stay valid even after the account is demoted, marked inactive, suspended, or deleted, so a former administrator retains full API-level control until the keys are manually purged. This CWE-613 (Insufficient Session Expiration) flaw carries a vendor CVSS of 9.1 and is fixed in 2.0.2. There is no public exploit identified at time of analysis and EPSS is low (0.16%), consistent with an insider/privilege-retention issue rather than mass internet exploitation.
Unauthenticated information disclosure in Apache Answer through 2.0.1 allows any remote user to retrieve deleted or pending answers via the single-answer read API path, provided the parent question remains publicly visible. The flaw bypasses moderation-state access controls, exposing content that was intentionally withheld from public view. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects limited real-world exploitation interest despite the high CVSS score.
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.
Insecure Direct Object Reference (IDOR) in Apache Answer through version 2.0.1 allows any authenticated user to delete uploaded files belonging to other users by supplying arbitrary file URLs to the avatar-cleanup endpoint. The root cause is a missing ownership check in the file-deletion logic (CWE-639), meaning the application accepts a user-controlled file URL and acts on it without verifying the requesting user has authority over that resource. No public exploit has been identified at time of analysis, but the attack requires only a valid account, making it low-friction once an attacker has registered or compromised any user.
Account takeover in Apache Answer through 2.0.1 allows unauthenticated remote attackers to seize arbitrary user accounts by exploiting a missing authorization check in the external-login OAuth email binding workflow. The attacker crafts a malicious confirmation link and socially engineers a target into clicking it, after which the attacker's external identity is silently bound to the victim's Answer account. No active exploitation has been identified (CISA KEV absent, EPSS at 7th percentile), but the SSVC framework flags the attack as automatable, making phishing-at-scale campaigns mechanically feasible.
Denial of service in Apache Answer through 2.0.1 allows unauthenticated remote attackers to exhaust CPU resources by sending a specially crafted Accept-Language HTTP header that triggers runaway parsing logic. The root cause is improper handling of a length parameter inconsistency (CWE-400) during header processing, meaning any unauthenticated HTTP request reaching the application can be weaponized for resource exhaustion. No public exploit code or CISA KEV listing has been identified at time of analysis, and the Apache Software Foundation has released a remediated version 2.0.2.
Stack-based buffer overflow in Apache Lucy (all versions) enables potential arbitrary code execution through crafted input triggering memory corruption in the retired C-based search library. All versions are affected with no patch planned, as the Apache Software Foundation has officially retired the project. No public exploit or active exploitation has been identified at time of analysis, but the absence of any future fix makes this a permanent unresolved risk for any remaining deployments.
Memory allocation with excessive size value in Apache Lucy (all versions) enables potential denial-of-service and information disclosure against a retired, unsupported search library. The vulnerability stems from CWE-789, where the library processes externally supplied size values without adequate bounds checking, potentially allowing an attacker to trigger abnormal memory allocation behaviour. No patch will ever be released - the Apache Software Foundation has officially retired Lucy and explicitly recommends migration to an alternative; no public exploit has been identified at time of analysis.
Insecure deserialization (CWE-502) in Apache Lucy affects all versions of this retired full-text search engine library, allowing an attacker who can supply crafted serialized data to a Lucy-backed application to corrupt reconstructed object state and potentially achieve code execution or logic abuse during deserialization. Because Apache Lucy is retired, the ASF has explicitly declined to ship a fix, so exposure is permanent for any deployment still using it. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV.
Uncontrolled Recursion in Apache Lucy, a retired full-text search library, enables remote unauthenticated attackers to crash the service via a crafted input, resulting in a complete denial of availability across all versions ever released. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms low-complexity, unauthenticated network exploitation with no confidentiality or integrity impact. No patch exists or will be issued by the Apache Software Foundation, as the project is officially retired; EPSS is low at 0.15% (5th percentile) and no active exploitation (CISA KEV) has been identified at time of analysis.
Unauthenticated information disclosure in DHL Shipping Germany for WooCommerce (versions before 4.0.1) exposes stored shipping labels - each containing customer name and postal address - to any visitor who can request predictable filenames from the label storage directory. The plugin relies exclusively on an Apache .htaccess file for directory access control, which nginx and other non-Apache web servers silently ignore, leaving the directory fully browsable over the network. A publicly available exploit exists (via WPScan), though EPSS of 0.14% at the 4th percentile indicates low observed exploitation activity, and the vulnerability is not listed in the CISA KEV catalog.
Resource exhaustion in Apache Qpid Proton-J through 0.34.1 allows authenticated AMQP clients to trigger unbounded server-side resource consumption by sending a delivery composed of an arbitrarily large number of transfer frames - a limit the library fails to enforce. The root cause (CWE-770) is an absent cap on per-delivery transfer frame counts during message ingestion, not a memory corruption or code execution class flaw. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; the primary risk is targeted denial of service against messaging infrastructure by any authenticated AMQP peer.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows authenticated AMQP clients to exhaust server CPU by sending a crafted disposition frame carrying large or illegal delivery ranges. The library's naive range handling iterates without bounds validation, causing unbounded CPU consumption that can starve legitimate connections. No public exploit identified at time of analysis; vendor-released fix is available in version 0.35.0.
Denial of service in Apache Qpid Broker-J through 10.0.1 allows authenticated session participants to exhaust broker resources by deliberately exceeding the AMQP session flow control incoming window. The broker fails to enforce adequate limits on resource allocation when a session window is overflowed, enabling a malicious but authenticated client to destabilize or crash the broker. No public exploit code exists at time of analysis, and no confirmed active exploitation has been reported.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows authenticated remote attackers to render the messaging endpoint unresponsive by deliberately exceeding the AMQP session flow control incoming window, triggering unbounded resource consumption. The root cause is CWE-770 - insufficient throttling of resource allocation - a well-understood class of flaw in protocol session management. No active exploitation has been confirmed and no public exploit code is known at time of analysis; the vendor has released a fix in version 0.35.0.
Unauthenticated remote denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting uncontrolled recursion during type-nesting processing, which exhausts the JVM call stack and triggers a StackOverflowError. The attack requires no credentials and no user interaction against any reachable broker instance. No public exploit identified at time of analysis; EPSS of 0.19% (9th percentile) indicates low real-world exploitation probability. Vendor-released patch: 10.1.0.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows unauthenticated remote attackers to crash the service by sending AMQP messages with deeply nested type structures that exhaust the JVM call stack via a StackOverflowError. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial, unauthenticated network exploitation with no user interaction required, targeting availability exclusively. No active exploitation has been confirmed - this vulnerability is absent from CISA KEV and carries a low EPSS score of 0.21% (11th percentile) - but the zero-prerequisite attack path warrants prompt patching for any internet-facing AMQP deployment.
Unauthenticated denial-of-service in Apache Qpid Broker-J through 10.0.1 allows any network-reachable attacker to crash or hang the broker by sending crafted AMQP protocol messages that exploit improper type size/count validation, triggering unbounded memory allocation. The flaw resides in the pre-authentication protocol parsing path, requiring no credentials, user interaction, or special configuration. No active exploitation is confirmed by CISA KEV, and the EPSS score of 0.19% (9th percentile) indicates minimal observed exploitation activity despite the straightforward attack vector.
Remote unauthenticated denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting unbounded symbol value caching in the AMQP message processing layer. A pre-authentication attacker can exhaust broker resources without supplying any credentials, crashing or hanging the service. No active exploitation is confirmed (not in CISA KEV), and EPSS at 0.21% (11th percentile) indicates low exploitation probability at time of analysis, though the network-accessible, zero-complexity attack path keeps it a meaningful patching priority for exposed deployments.
Uncontrolled resource consumption in Apache Qpid ProtonJ2 through version 1.1.0 allows authenticated AMQP clients to cause denial of service by sending deliveries composed of an unbounded number of transfer frames. Because the library imposed no upper limit on how many AMQP transfer frames could constitute a single incoming delivery, a malicious but authenticated client can force unbounded heap accumulation, leading to excessive memory usage and potential JVM failure. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patch version 1.2.0 is available.
Session flow control enforcement in Apache Qpid ProtonJ2 (versions through 1.1.0) can be bypassed by an authenticated attacker who sends data exceeding the negotiated incoming flow control window, potentially causing denial of service on the receiving side. The AMQP session-level window is a back-pressure mechanism; failure to enforce it can lead to unbounded memory consumption or processing overload in the message broker or client. No public exploit code and no CISA KEV listing have been identified at time of analysis. The vendor-released fix is version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a remote unauthenticated attacker to crash the messaging service by sending AMQP messages with maliciously crafted type nesting that triggers an uncontrolled recursive call stack, resulting in a StackOverflowError. The flaw (CWE-674) is exploitable without authentication over the network with low attack complexity, making it trivially reachable against any exposed ProtonJ2 endpoint. No active exploitation has been confirmed (not in CISA KEV) and EPSS sits at 0.21% (11th percentile), suggesting minimal observed exploitation activity at time of analysis despite the ease of triggering the condition.
Remote unauthenticated denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a network attacker to exhaust server memory by sending AMQP messages with maliciously crafted type size or count fields, triggering uncontrolled allocation. The vulnerability (CWE-789) requires no authentication or user interaction and is exploitable directly over the network with low complexity, making it trivially reachable in any exposed deployment. No active exploitation has been confirmed in CISA KEV, and the EPSS score of 0.21% (11th percentile) suggests limited real-world exploitation interest at time of analysis; a vendor-released fix is available in version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through 1.1.0 allows unauthenticated remote attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values during pre-authentication message processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials or user interaction are required, and the attack can be executed at low complexity from any network-accessible position. No public exploit or CISA KEV listing exists at time of analysis, though the trivial exploitation conditions make this a realistic threat against any Qpid ProtonJ2 endpoint exposed to untrusted networks.
Uncontrolled resource consumption in Apache Qpid Proton-Dotnet through 1.0.0 allows an authenticated AMQP client to trigger denial of service by sending a single delivery split across an unbounded number of transfer frames. The .NET implementation of the AMQP 1.0 toolkit lacked any enforced ceiling on incoming transfer frames per delivery, meaning a malicious but authenticated peer can exhaust receiver memory or CPU without restriction. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; the fix is available in version 1.1.0.
Denial of service in Apache Qpid Proton-Dotnet through 1.0.0 allows an authenticated AMQP peer to exhaust CPU resources on the target host by sending a crafted disposition frame containing large or illegal delivery ranges. The library's naive range-iteration logic processes these unbounded ranges without safeguards, causing the consuming thread to spin and starve legitimate message processing. Vendor-released patch version 1.1.0 is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Session flow control enforcement failure in Apache Qpid Proton-Dotnet through version 1.0.0 allows an authenticated attacker to deliberately exceed the AMQP incoming session flow control window, potentially causing denial of service on affected messaging endpoints. The vulnerability is rated 'important' by Apache and affects the .NET client library for AMQP-based messaging infrastructure. No public exploit code or active exploitation has been identified; vendor-confirmed fix is available in version 1.1.0.
Denial of service in Apache Qpid Proton-Dotnet 1.0.0 and earlier allows a pre-authentication remote attacker to crash the AMQP service by submitting messages with deeply nested type structures, triggering a StackOverflowError. The CVSS 7.5 (High) reflects a fully network-exposed, unauthenticated attack path with complete availability impact. No active exploitation has been confirmed (EPSS: 0.19%, 9th percentile; no CISA KEV listing), and the vendor has released a direct fix in version 1.1.0.
Excessive memory allocation in Apache Qpid Proton Dotnet through 1.0.0 enables pre-authentication denial of service via crafted AMQP messages. The .NET AMQP client library fails to properly validate type size or count fields during message parsing, allowing a remote unauthenticated attacker to trigger unbounded memory allocation and exhaust available resources. No public exploit code has been identified at time of analysis, but the pre-authentication vector and network reachability of AMQP services make this a realistic threat to messaging infrastructure.
Pre-authentication denial of service in Apache Qpid Proton-Dotnet through version 1.0.0 allows remote unauthenticated attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values. Because the vulnerability is reachable before any authentication handshake completes, no credentials or prior access are required to trigger resource exhaustion. No public exploit or KEV listing is identified at time of analysis, but the pre-auth nature and low attack complexity make this a meaningful availability risk for any internet- or network-exposed AMQP endpoint using the affected .NET library.
Unbounded echo flow responses in Apache Qpid Broker-J (all versions through 10.0.1) allow an authenticated AMQP 1.0 client to exhaust broker resources and cause denial of service by flooding the broker with unanswered echo flow frames. The root cause is absent rate-limiting on echo flow response logic in the qpid-broker-plugins-amqp-1-0-protocol plugin. No public exploit code or CISA KEV listing has been identified; the vendor has released a fix in version 10.1.0.
Resource exhaustion in Apache Qpid Broker-J through version 10.0.1 enables authenticated remote attackers to cause denial of service by submitting an unbounded number of AMQP 1.0 transfer frames within a single incoming delivery, with no broker-side enforcement of a per-delivery frame ceiling. The broker's AMQP 1.0 protocol plugin lacks the necessary throttling logic, meaning sustained abuse can exhaust memory and CPU resources and deny service to legitimate messaging clients. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; a vendor-released patch is available in version 10.1.0.
Denial of service in Apache Qpid Broker-J through version 10.0.1 allows authenticated AMQP 1.0 clients to exhaust broker CPU resources by sending crafted disposition frames containing large or illegal delivery-ID ranges. The broker's naive range iteration logic processes these ranges without bounds enforcement, causing excessive CPU consumption that degrades or halts message brokering for all connected clients. No public exploit code and no confirmed active exploitation are known at time of analysis; vendor-released fix 10.1.0 is available.
Excessive heap allocation in Apache Qpid Proton-J's AMQP type parser exposes any network-accessible AMQP endpoint to unauthenticated denial-of-service before an authentication handshake completes. Malformed AMQP frames containing attacker-controlled size or count field values cause the Java library to allocate unbounded memory, leading to JVM heap exhaustion and service crash. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis, but the pre-authentication attack vector and zero-privilege requirement make this a high-priority patch target for any internet-exposed Proton-J deployment.
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.
Remote code and command injection in Apache Allura before 1.19.1 lets unauthenticated attackers smuggle attacker-controlled arguments into git command invocations through specially crafted inputs. Because Allura is a project-hosting and forge platform that shells out to git, this argument injection (CWE-88) can be leveraged to influence git behavior and, depending on the invoked subcommand, achieve command execution against the hosting server; no public exploit has been identified at time of analysis and EPSS exploitation probability is low (0.18%).
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 3.0.0 through 3.3.0 allows any DAG author to achieve arbitrary code execution in the Scheduler and API server by placing a crafted value in an operator's executor_config field. The serialization layer reconstructed exception nodes by calling import_string() on an attacker-controlled class name with no allowlist, enabling import and invocation of arbitrary callables such as subprocess.check_output or builtins.eval. Both affected components hold the metadata database credentials and JWT signing secret, making full infrastructure compromise a realistic outcome. No public exploit has been identified at time of analysis, but no non-default configuration is required. This is a distinct sink from CVE-2026-33264, meaning deployments that already patched that earlier advisory remain fully vulnerable and must upgrade again to apache-airflow 3.3.1.
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.
Remote code execution and scheduler-process disruption in Apache Airflow 3.3.0 stems from unguarded deserialization of task instance `next_kwargs` during the scheduler's unconditional `awaiting_input` sweep, a code path introduced as part of the 3.3.0 human-in-the-loop task rewrite. Any authenticated DAG author who can influence task state through the task execution API can supply a crafted payload that causes arbitrary module import and object instantiation inside the scheduler process, or terminate the scheduler job entirely. No public exploit has been identified at time of analysis, but a vendor-released patch exists in 3.3.1; deployments that previously patched CVE-2026-58076 are still vulnerable through this distinct code path and must upgrade.
Unsafe deserialization in Apache Airflow 3.3.0's Task SDK allows an authenticated DAG author to cause arbitrary module imports inside the scheduler process. By controlling a task instance's `next_kwargs` via the task execution API, an attacker can inject a crafted callback path that the scheduler's unconditional `awaiting_input` timeout sweep deserializes by re-running the `SyncCallback` constructor - triggering an import of the named module in the scheduler's process space. Because `SyncCallback` is itself an Airflow class, it bypasses the `allowed_deserialization_classes` allow-list, making tightening that setting ineffective. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS score of 8.8 reflects the severity of the potential scheduler process compromise.
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.
Authorization bypass in Apache Airflow's Backfill API (all versions prior to 3.3.1) allows any authenticated user holding edit permission on a single DAG to read, pause, cancel, and fail backfills belonging to any other DAG. The flaw is a type-parsing mismatch in FastAPI's dependency resolution layer: the authorization dependency parsed the `backfill_id` path parameter with Python's `int()` while the route handler declared `NonNegativeInt` via Pydantic, which in lax mode coerces inputs like `'42.0'` that `int()` rejects-causing the two components to authorize and act on different DAGs. Backfill IDs are sequential, making cross-DAG enumeration trivial; no public exploit code has been identified at time of analysis, though the technique is directly reproducible from the published patch diff.
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.
Server-impersonation via broken TLS hostname verification affects Apache HttpComponents Client 5.4 through 5.6.3 when applications use the asynchronous HttpClient, where the HostnameVerificationPolicy#BUILTIN setting is silently ignored. An adversary positioned to intercept and modify network traffic can present a valid certificate issued for an unrelated domain and the async client will accept it, defeating the core TLS server-identity check and exposing transmitted data. There is no public exploit identified at time of analysis and EPSS is very low (0.09%), but the CVSS base score is 9.1 and the classic (synchronous) HttpClient is explicitly unaffected.
Unauthenticated credential theft in the InstaWP Connect WordPress migration plugin (all versions ≤ 0.1.3.6) exposes database access details and API signatures on Apache servers during active migration windows. The plugin predictably derives its AES-256-CBC decryption passphrase as SHA256(migrate_key), where the migrate_key is directly leaked in the filename of the unprotected options file via Apache directory listing - allowing an attacker who finds the file to mathematically recover the encryption key and decrypt the options payload without any brute force. Recovery of the api_signature may enable downstream remote code execution via InstaWP's service API. No public exploit or CISA KEV listing has been confirmed at time of analysis, though the deterministic key derivation significantly reduces exploitation effort.
Server-Side Request Forgery in Apache Allura before 1.19.1 lets attackers abuse the project webhook feature to coerce the server into issuing arbitrary outbound HTTP requests, exposing internal services and cloud metadata endpoints. The flaw carries a CVSS 9.1 and is fixed in 1.19.1; it was disclosed via the Apache security team and oss-security on 2026-08-11. There is no public exploit identified at time of analysis and EPSS is low (0.20%, 11th percentile), indicating no observed weaponization yet.
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.
Unauthenticated classpath asset disclosure in Apache Tapestry 5.5.0 through 5.9.0 exposes arbitrary files on the Java classpath to remote attackers via specially crafted HTTP URLs. The tapestry-core component fails to restrict URL-based access to classpath resources, meaning attackers can retrieve sensitive files such as configuration files, properties files containing credentials, and compiled .class files. No public exploit code has been identified at time of analysis, but the attack requires no authentication, no user interaction, and minimal complexity - lowering the bar for exploitation significantly.
Command injection in Apache Ranger versions 0.6 through 2.8 allows attackers to inject and execute operating-system commands through improperly neutralized special elements (CWE-77), yielding full compromise of the host running the Ranger service. The NVD CVSS vector scores it 9.8 (network, low complexity, no privileges, no user interaction) with high confidentiality, integrity, and availability impact, meaning a successful exploit can read, alter, and destroy data on the affected component. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV; EPSS estimates a 1.01% 30-day exploitation probability (60th percentile).
SQL injection in Apache Ranger allows remote attackers to inject arbitrary SQL through the application's data-access layer, exposing the backing policy/audit database to full read, modification, and destruction. Because Ranger is the centralized authorization and access-control service for Hadoop and related big-data platforms, compromise here can undermine security policy enforcement across an entire data estate. Rated CVSS 9.8; no public exploit identified at time of analysis, EPSS is low (0.21%, 12th percentile), and the flaw is fixed in version 2.9.0.
Privilege escalation in Apache Ranger versions 2.8.0 and earlier allows an attacker to elevate their effective permissions by manipulating a URL parameter, undermining the very access-control layer Ranger is meant to enforce across Hadoop-ecosystem services. Apache rates it CVSS 9.8 with a network, low-complexity, no-privilege vector, though the 'privilege escalation' framing implies a pre-existing foothold that is worth verifying. There is no public exploit identified at time of analysis, and the EPSS score is low (0.19%, 9th percentile), indicating no observed mass-exploitation activity yet.
Remote code execution in Apache Ranger versions up to and including 2.8.0 arises from JDBC URL injection (CWE-94), letting an attacker who can influence a database connection string coerce the server into loading attacker-controlled JDBC driver behavior and executing arbitrary code on the Ranger host. This flaw affects the centralized authorization framework used to govern access across Hadoop-ecosystem services, so compromise undermines the very control plane meant to enforce data security. There is no public exploit identified at time of analysis and EPSS is low (0.36%, 29th percentile), but the fix in 2.9.0 and the critical 9.8 CVSS warrant prompt patching.
Remote code execution in Apache Ranger 2.8.0 and earlier arises from arbitrary Java class instantiation in the plugin-schema-registry component, letting an attacker who can reach the affected interface load and run attacker-controlled classes and achieve full compromise (CWE-94). The flaw carries a critical CVSS 9.8 and is fixed in Ranger 2.9.0. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, with EPSS at a modest 0.58% (45th percentile).
Remote code execution in Apache Ranger versions up to and including 2.8.0 stems from unsafe script evaluation in the GraalScriptEngineCreator component, letting an attacker inject and execute arbitrary code (CWE-94) on the Ranger host. Because Ranger is the central authorization and data-governance layer for Hadoop-ecosystem services, compromise can undermine access control across an entire big-data platform. There is no public exploit identified at time of analysis, it is not on CISA KEV, and EPSS is modest (0.34%, 26th percentile), but the 9.8 CVSS rating reflects the potential for full host compromise once conditions are met.
Unauthenticated access to Apache Ranger Download APIs on versions 2.8.0 and earlier exposes sensitive authorization policy data to any remote attacker with network connectivity. The missing authentication check (CWE-306) means no credentials or privileges are required to invoke these endpoints and retrieve their output. No public exploit code has been identified at time of analysis, but the low complexity and zero-authentication nature of the CVSS vector (AV:N/AC:L/PR:N/UI:N) makes this trivially exploitable by any attacker who can reach the Ranger Admin interface.
TLS hostname verification failure in Apache Ranger Client Code allows network-positioned attackers to intercept sensitive traffic via man-in-the-middle attacks against all deployments running version 2.8.0 or earlier. The client fails to validate that a server's TLS certificate hostname matches the actual server being contacted (CWE-297), meaning a forged or mismatched certificate will be accepted silently. A vendor-released patch is available in version 2.9.0; no public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
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.
Brute-force credential attacks against Apache Ranger's UnixAuth component are possible in all versions up to and including 2.8.0, because the authentication endpoint imposes no rate limiting, account lockout, or anti-automation controls (CWE-307). Any deployment that has explicitly configured UnixAuth - a configuration the vendor labels as not recommended for production - exposes its Ranger admin interface to automated password-guessing from unauthenticated network attackers. No active exploitation is recorded in CISA KEV and no public POC has been identified at time of analysis, but the unauthenticated network vector (AV:N/PR:N/AC:L) makes automated credential attacks trivially executable against any network-reachable instance.
Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the database by sending a single crafted malformed frame. Improper validation of length fields (CWE-789) causes IoTDB to attempt arbitrarily large heap allocations, exhausting JVM memory and terminating the process with an OutOfMemoryError. Versions before 1.3.8 on the 1.x branch and 2.0.0 through 2.0.8 on the 2.0.x branch are affected; no public exploit code or CISA KEV listing has been identified at time of analysis.
Denial of service in the Go implementation of Apache Fory allows unauthenticated remote attackers to crash affected services by sending crafted serialized data containing malformed type metadata, triggering an uncaught Go runtime panic. Affected versions span 0.16.0 through 1.5.0 (exclusive), while all non-Go language implementations remain unaffected. No public exploit code or active exploitation (CISA KEV) has been identified; the EPSS score of 0.18% (8th percentile) corroborates low current exploitation activity despite the high CVSS base score.
Heap type confusion in the Apache Fory C++ deserialization engine (versions 0.14.0 up to but not including 1.5.0) lets a crafted payload bypass type-compatibility checks during polymorphic smart-pointer deserialization, so an object of an incompatible type is handled as its declared base type. Because CWE-502 untrusted-data handling here corrupts memory rather than merely mis-parsing values, an attacker who controls serialized input can trigger undefined behavior ranging from denial of service to arbitrary code execution. This is rated CVSS 9.8 and is fixed in 1.5.0; there is no public exploit identified at time of analysis and EPSS is low at 0.21%.
Out-of-bounds heap read in Apache Fory C++ versions 0.14.0 through 1.4.x allows attackers supplying crafted deserialization payloads to trigger information disclosure or denial of service. The flaw resides specifically in the tagged integer fast-path deserializer and only manifests when the application processes structs with tagged integer fields. No public exploit or active exploitation has been identified at time of analysis, and a vendor-released patch is available in version 1.5.0.
Command injection in sysPass's backup service allows any authenticated administrator to execute arbitrary OS commands as the web server process user by storing shell metacharacters in the backup path configuration setting and triggering a backup operation. Because sysPass is a self-hosted password manager, successful exploitation grants direct read access to the master encryption key and entire credential vault, enabling mass credential disclosure and lateral movement to every system whose passwords are stored in sysPass. A public proof-of-concept is available via the referenced gist (https://gist.github.com/W40X/6747ba1b7da7bb69b0c0e162628df279); no CISA KEV listing was identified at time of analysis.
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.
Cross-user HTTP response poisoning in Traefik's default reverse proxy allows an unauthenticated remote attacker using HTTP/2 or HTTP/3 to smuggle responses into other clients' backend connections, potentially delivering authenticated or private content from one user to another. All supported Traefik branches through v2.11.52, v3.6.23, and v3.7.8 are affected in default configuration when fronting Go net/http or gunicorn/Flask backends, which are confirmed 'armed' (respond to CONNECT with keep-alive non-2xx without draining the body). A proof-of-concept is publicly available demonstrating reliable cross-user poisoning including a cascade scenario where 8 of 8 sequential victims read responses that were not their own; no CISA KEV listing was present at time of analysis.
SQL injection in the Apache Portable Runtime Utility (APR-util) affects the apr_dbd_oracle database provider in versions 1.6.0 through 1.6.3, letting remote attackers inject arbitrary SQL through an application that relies on this DBD backend for query construction or escaping. Rated CVSS 9.1 with high confidentiality and integrity impact but no availability impact, it allows unauthorized reading and modification of Oracle-backed data. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Heap-based buffer overflow in Apache Portable Runtime Utility's redis client component allows remote unauthenticated attackers to crash applications that use the library, resulting in a denial of service. Affected versions span APR-util 1.6.0 through 1.6.3; version 1.6.4 resolves the issue per Apache's advisory on the oss-security mailing list. No public exploit code and no CISA KEV listing have been identified at time of analysis, though SSVC classifies the flaw as automatable with partial technical impact, indicating it could be scripted for broad scanning.
Heap-based buffer overflow in Apache Portable Runtime Utility's memcached client component (versions 1.3.0 through 1.6.3) allows remote unauthenticated attackers to crash affected applications, causing denial of service. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms full availability impact with no confidentiality or integrity exposure. No public exploit identified at time of analysis, but SSVC marks this as automatable, meaning scripted mass scanning is feasible once attack primitives are established.
Authorization scope escalation in Apache CXF's OAuth2 Dynamic Client Registration endpoint allows any registering client to self-assign privileged scopes by supplying arbitrary `scope` values in the registration request, which the authorization server stores verbatim without validating against a server-defined allowlist. Affected versions span the 3.x, 4.1.x, and 4.2.x release lines; patched releases 3.6.12, 4.1.8, and 4.2.3 are available per the Apache advisory. No public exploit or active exploitation has been identified at time of analysis, but the straightforward exploitation path - crafting a single registration request - makes this a meaningful authorization bypass risk for any deployment exposing CXF's OAuth2 AS with Dynamic Client Registration enabled.
Apache CXF's JwtRequestCodeFilter blindly copies all claims from a validly-signed JWT request object into the OAuth2 authorization parameter map, including security-sensitive fields that must not be client-controlled: code_challenge, code_challenge_method, nonce, and state. Affected are all Apache CXF deployments using this filter for OAuth2/OIDC authorization code flows prior to versions 4.2.3, 4.1.8, and 3.6.12. An OAuth2 client with a known or compromised client_secret can craft a signed request JWT that overrides the PKCE parameters established in the outer HTTP request, effectively nullifying PKCE authorization code binding and OIDC replay protection. No public exploit code or CISA KEV listing has been identified at time of analysis.
Authentication bypass in Apache CXF's OIDC relying-party implementation allows network-accessible attackers to forge self-issued ID tokens that skip all required OpenID Connect claim checks - issuer, subject, audience, time bounds, and sub_jwk binding - effectively impersonating any user identity. Affected are all Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 when the relying party is explicitly configured to accept self-issued OIDC tokens, a non-default setting. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface is constrained to a narrow set of deliberately misconfigured deployments.
Apache CXF's DefaultEncryptingCodeDataProvider allows captured OAuth 2.0 authorization codes to be redeemed an unlimited number of times, violating RFC 6749's single-use requirement. The removeCodeGrant() method that should invalidate a code after first exchange fails to do so, meaning any attacker who intercepts or obtains a legitimate authorization code can replay it repeatedly to obtain additional access tokens. No public exploit has been identified at time of analysis, and the issue is addressed in patched releases 4.2.3, 4.1.8, and 3.6.12.
Token revocation bypass in Apache CXF's DefaultEncryptingOAuthDataProvider allows revoked OAuth access and refresh tokens to remain functionally valid indefinitely - the provider continues to decrypt them successfully and TokenIntrospectionService returns active:true in direct violation of RFC 7009 and RFC 7662 mandates. All Apache CXF deployments using this built-in OAuth data provider and relying on token revocation as a security control are affected across the 3.6.x, 4.1.x, and 4.2.x branches. An attacker or suspended user who retains a revoked token can continue accessing protected resources as though revocation never occurred, bypassing intended authorization boundaries. No public exploit has been identified at time of analysis, though the attack requires no tooling beyond a standard HTTP client.
XML External Entity injection in Apache CXF's WSDL import processing allows attackers who can influence imported WSDL or XSD documents to bypass XXE protections applied to the top-level WSDL. CXF correctly hardens top-level WSDL parsing via StaxUtils, but delegates all <wsdl:import> and <xsd:import> resolution to WSDL4J, which lacks equivalent DOCTYPE and external entity restrictions - creating a security boundary mismatch that nullifies the top-level protections. No public exploit has been identified at time of analysis, but CWE-611 is a well-understood attack class with established tooling; successful exploitation against vulnerable deployments can yield arbitrary server-side file reads and SSRF. Vendor-released patches are available across three active release branches.
Authorization Code Substitution in Apache CXF's OpenID Connect Relying Party implementation allows remote attackers to hijack authenticated sessions when CXF is deployed in Hybrid Flow mode with a non-compliant or misconfigured Identity Provider that omits the c_hash parameter. Successful exploitation yields full authenticated access equivalent to account takeover, with high confidentiality and integrity impact. No public exploit has been identified at time of analysis, but SSVC classifies the attack as automatable with total technical impact once the prerequisite IdP condition is present.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
Denial of service persists in Apache CXF due to an incomplete remediation of CVE-2026-50645, allowing unauthenticated network attackers to exhaust server resources by submitting messages containing an excessive number of MIME attachment headers. All Apache CXF deployments running versions prior to 4.2.3, 4.1.8, or 3.6.12 remain vulnerable despite having applied the prior patch. No public exploit code or active exploitation has been identified at time of analysis, but the bypass-of-fix nature of this vulnerability means any organization that patched CVE-2026-50645 and considered itself remediated must re-patch.
Uncontrolled resource consumption in Apache CXF's JAX-RS form parameter processing enables remote denial-of-service attacks against any exposed endpoint accepting form-encoded requests. The framework provides a 'maxFormParameterCount' configuration knob but sets no default ceiling, meaning unpatched deployments will parse arbitrarily large parameter sets until memory or CPU is exhausted. Fixed versions (4.2.3, 4.1.8, and 3.6.12) enforce a default cap of 500 parameters; no public exploit or CISA KEV listing has been identified at time of analysis.
Unbounded attachment ingestion in Apache CXF enables remote denial-of-service against any endpoint that processes multipart messages. Versions prior to 4.2.3, 4.1.8, and 3.6.12 imposed no default ceiling on the 'attachment-max-size' parameter, allowing attackers to exhaust server memory or processing capacity by submitting arbitrarily large attachments. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the low attack complexity makes this a realistic threat for internet-exposed CXF deployments.
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.
Privileged API access in Apache Answer through 2.0.1 persists after an administrator loses their authority: keys issued to an admin stay valid even after the account is demoted, marked inactive, suspended, or deleted, so a former administrator retains full API-level control until the keys are manually purged. This CWE-613 (Insufficient Session Expiration) flaw carries a vendor CVSS of 9.1 and is fixed in 2.0.2. There is no public exploit identified at time of analysis and EPSS is low (0.16%), consistent with an insider/privilege-retention issue rather than mass internet exploitation.
Unauthenticated information disclosure in Apache Answer through 2.0.1 allows any remote user to retrieve deleted or pending answers via the single-answer read API path, provided the parent question remains publicly visible. The flaw bypasses moderation-state access controls, exposing content that was intentionally withheld from public view. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects limited real-world exploitation interest despite the high CVSS score.
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.
Insecure Direct Object Reference (IDOR) in Apache Answer through version 2.0.1 allows any authenticated user to delete uploaded files belonging to other users by supplying arbitrary file URLs to the avatar-cleanup endpoint. The root cause is a missing ownership check in the file-deletion logic (CWE-639), meaning the application accepts a user-controlled file URL and acts on it without verifying the requesting user has authority over that resource. No public exploit has been identified at time of analysis, but the attack requires only a valid account, making it low-friction once an attacker has registered or compromised any user.
Account takeover in Apache Answer through 2.0.1 allows unauthenticated remote attackers to seize arbitrary user accounts by exploiting a missing authorization check in the external-login OAuth email binding workflow. The attacker crafts a malicious confirmation link and socially engineers a target into clicking it, after which the attacker's external identity is silently bound to the victim's Answer account. No active exploitation has been identified (CISA KEV absent, EPSS at 7th percentile), but the SSVC framework flags the attack as automatable, making phishing-at-scale campaigns mechanically feasible.
Denial of service in Apache Answer through 2.0.1 allows unauthenticated remote attackers to exhaust CPU resources by sending a specially crafted Accept-Language HTTP header that triggers runaway parsing logic. The root cause is improper handling of a length parameter inconsistency (CWE-400) during header processing, meaning any unauthenticated HTTP request reaching the application can be weaponized for resource exhaustion. No public exploit code or CISA KEV listing has been identified at time of analysis, and the Apache Software Foundation has released a remediated version 2.0.2.
Stack-based buffer overflow in Apache Lucy (all versions) enables potential arbitrary code execution through crafted input triggering memory corruption in the retired C-based search library. All versions are affected with no patch planned, as the Apache Software Foundation has officially retired the project. No public exploit or active exploitation has been identified at time of analysis, but the absence of any future fix makes this a permanent unresolved risk for any remaining deployments.
Memory allocation with excessive size value in Apache Lucy (all versions) enables potential denial-of-service and information disclosure against a retired, unsupported search library. The vulnerability stems from CWE-789, where the library processes externally supplied size values without adequate bounds checking, potentially allowing an attacker to trigger abnormal memory allocation behaviour. No patch will ever be released - the Apache Software Foundation has officially retired Lucy and explicitly recommends migration to an alternative; no public exploit has been identified at time of analysis.
Insecure deserialization (CWE-502) in Apache Lucy affects all versions of this retired full-text search engine library, allowing an attacker who can supply crafted serialized data to a Lucy-backed application to corrupt reconstructed object state and potentially achieve code execution or logic abuse during deserialization. Because Apache Lucy is retired, the ASF has explicitly declined to ship a fix, so exposure is permanent for any deployment still using it. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV.
Uncontrolled Recursion in Apache Lucy, a retired full-text search library, enables remote unauthenticated attackers to crash the service via a crafted input, resulting in a complete denial of availability across all versions ever released. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms low-complexity, unauthenticated network exploitation with no confidentiality or integrity impact. No patch exists or will be issued by the Apache Software Foundation, as the project is officially retired; EPSS is low at 0.15% (5th percentile) and no active exploitation (CISA KEV) has been identified at time of analysis.
Unauthenticated information disclosure in DHL Shipping Germany for WooCommerce (versions before 4.0.1) exposes stored shipping labels - each containing customer name and postal address - to any visitor who can request predictable filenames from the label storage directory. The plugin relies exclusively on an Apache .htaccess file for directory access control, which nginx and other non-Apache web servers silently ignore, leaving the directory fully browsable over the network. A publicly available exploit exists (via WPScan), though EPSS of 0.14% at the 4th percentile indicates low observed exploitation activity, and the vulnerability is not listed in the CISA KEV catalog.
Resource exhaustion in Apache Qpid Proton-J through 0.34.1 allows authenticated AMQP clients to trigger unbounded server-side resource consumption by sending a delivery composed of an arbitrarily large number of transfer frames - a limit the library fails to enforce. The root cause (CWE-770) is an absent cap on per-delivery transfer frame counts during message ingestion, not a memory corruption or code execution class flaw. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; the primary risk is targeted denial of service against messaging infrastructure by any authenticated AMQP peer.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows authenticated AMQP clients to exhaust server CPU by sending a crafted disposition frame carrying large or illegal delivery ranges. The library's naive range handling iterates without bounds validation, causing unbounded CPU consumption that can starve legitimate connections. No public exploit identified at time of analysis; vendor-released fix is available in version 0.35.0.
Denial of service in Apache Qpid Broker-J through 10.0.1 allows authenticated session participants to exhaust broker resources by deliberately exceeding the AMQP session flow control incoming window. The broker fails to enforce adequate limits on resource allocation when a session window is overflowed, enabling a malicious but authenticated client to destabilize or crash the broker. No public exploit code exists at time of analysis, and no confirmed active exploitation has been reported.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows authenticated remote attackers to render the messaging endpoint unresponsive by deliberately exceeding the AMQP session flow control incoming window, triggering unbounded resource consumption. The root cause is CWE-770 - insufficient throttling of resource allocation - a well-understood class of flaw in protocol session management. No active exploitation has been confirmed and no public exploit code is known at time of analysis; the vendor has released a fix in version 0.35.0.
Unauthenticated remote denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting uncontrolled recursion during type-nesting processing, which exhausts the JVM call stack and triggers a StackOverflowError. The attack requires no credentials and no user interaction against any reachable broker instance. No public exploit identified at time of analysis; EPSS of 0.19% (9th percentile) indicates low real-world exploitation probability. Vendor-released patch: 10.1.0.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows unauthenticated remote attackers to crash the service by sending AMQP messages with deeply nested type structures that exhaust the JVM call stack via a StackOverflowError. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial, unauthenticated network exploitation with no user interaction required, targeting availability exclusively. No active exploitation has been confirmed - this vulnerability is absent from CISA KEV and carries a low EPSS score of 0.21% (11th percentile) - but the zero-prerequisite attack path warrants prompt patching for any internet-facing AMQP deployment.
Unauthenticated denial-of-service in Apache Qpid Broker-J through 10.0.1 allows any network-reachable attacker to crash or hang the broker by sending crafted AMQP protocol messages that exploit improper type size/count validation, triggering unbounded memory allocation. The flaw resides in the pre-authentication protocol parsing path, requiring no credentials, user interaction, or special configuration. No active exploitation is confirmed by CISA KEV, and the EPSS score of 0.19% (9th percentile) indicates minimal observed exploitation activity despite the straightforward attack vector.
Remote unauthenticated denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting unbounded symbol value caching in the AMQP message processing layer. A pre-authentication attacker can exhaust broker resources without supplying any credentials, crashing or hanging the service. No active exploitation is confirmed (not in CISA KEV), and EPSS at 0.21% (11th percentile) indicates low exploitation probability at time of analysis, though the network-accessible, zero-complexity attack path keeps it a meaningful patching priority for exposed deployments.
Uncontrolled resource consumption in Apache Qpid ProtonJ2 through version 1.1.0 allows authenticated AMQP clients to cause denial of service by sending deliveries composed of an unbounded number of transfer frames. Because the library imposed no upper limit on how many AMQP transfer frames could constitute a single incoming delivery, a malicious but authenticated client can force unbounded heap accumulation, leading to excessive memory usage and potential JVM failure. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patch version 1.2.0 is available.
Session flow control enforcement in Apache Qpid ProtonJ2 (versions through 1.1.0) can be bypassed by an authenticated attacker who sends data exceeding the negotiated incoming flow control window, potentially causing denial of service on the receiving side. The AMQP session-level window is a back-pressure mechanism; failure to enforce it can lead to unbounded memory consumption or processing overload in the message broker or client. No public exploit code and no CISA KEV listing have been identified at time of analysis. The vendor-released fix is version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a remote unauthenticated attacker to crash the messaging service by sending AMQP messages with maliciously crafted type nesting that triggers an uncontrolled recursive call stack, resulting in a StackOverflowError. The flaw (CWE-674) is exploitable without authentication over the network with low attack complexity, making it trivially reachable against any exposed ProtonJ2 endpoint. No active exploitation has been confirmed (not in CISA KEV) and EPSS sits at 0.21% (11th percentile), suggesting minimal observed exploitation activity at time of analysis despite the ease of triggering the condition.
Remote unauthenticated denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a network attacker to exhaust server memory by sending AMQP messages with maliciously crafted type size or count fields, triggering uncontrolled allocation. The vulnerability (CWE-789) requires no authentication or user interaction and is exploitable directly over the network with low complexity, making it trivially reachable in any exposed deployment. No active exploitation has been confirmed in CISA KEV, and the EPSS score of 0.21% (11th percentile) suggests limited real-world exploitation interest at time of analysis; a vendor-released fix is available in version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through 1.1.0 allows unauthenticated remote attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values during pre-authentication message processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials or user interaction are required, and the attack can be executed at low complexity from any network-accessible position. No public exploit or CISA KEV listing exists at time of analysis, though the trivial exploitation conditions make this a realistic threat against any Qpid ProtonJ2 endpoint exposed to untrusted networks.
Uncontrolled resource consumption in Apache Qpid Proton-Dotnet through 1.0.0 allows an authenticated AMQP client to trigger denial of service by sending a single delivery split across an unbounded number of transfer frames. The .NET implementation of the AMQP 1.0 toolkit lacked any enforced ceiling on incoming transfer frames per delivery, meaning a malicious but authenticated peer can exhaust receiver memory or CPU without restriction. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; the fix is available in version 1.1.0.
Denial of service in Apache Qpid Proton-Dotnet through 1.0.0 allows an authenticated AMQP peer to exhaust CPU resources on the target host by sending a crafted disposition frame containing large or illegal delivery ranges. The library's naive range-iteration logic processes these unbounded ranges without safeguards, causing the consuming thread to spin and starve legitimate message processing. Vendor-released patch version 1.1.0 is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Session flow control enforcement failure in Apache Qpid Proton-Dotnet through version 1.0.0 allows an authenticated attacker to deliberately exceed the AMQP incoming session flow control window, potentially causing denial of service on affected messaging endpoints. The vulnerability is rated 'important' by Apache and affects the .NET client library for AMQP-based messaging infrastructure. No public exploit code or active exploitation has been identified; vendor-confirmed fix is available in version 1.1.0.
Denial of service in Apache Qpid Proton-Dotnet 1.0.0 and earlier allows a pre-authentication remote attacker to crash the AMQP service by submitting messages with deeply nested type structures, triggering a StackOverflowError. The CVSS 7.5 (High) reflects a fully network-exposed, unauthenticated attack path with complete availability impact. No active exploitation has been confirmed (EPSS: 0.19%, 9th percentile; no CISA KEV listing), and the vendor has released a direct fix in version 1.1.0.
Excessive memory allocation in Apache Qpid Proton Dotnet through 1.0.0 enables pre-authentication denial of service via crafted AMQP messages. The .NET AMQP client library fails to properly validate type size or count fields during message parsing, allowing a remote unauthenticated attacker to trigger unbounded memory allocation and exhaust available resources. No public exploit code has been identified at time of analysis, but the pre-authentication vector and network reachability of AMQP services make this a realistic threat to messaging infrastructure.
Pre-authentication denial of service in Apache Qpid Proton-Dotnet through version 1.0.0 allows remote unauthenticated attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values. Because the vulnerability is reachable before any authentication handshake completes, no credentials or prior access are required to trigger resource exhaustion. No public exploit or KEV listing is identified at time of analysis, but the pre-auth nature and low attack complexity make this a meaningful availability risk for any internet- or network-exposed AMQP endpoint using the affected .NET library.
Unbounded echo flow responses in Apache Qpid Broker-J (all versions through 10.0.1) allow an authenticated AMQP 1.0 client to exhaust broker resources and cause denial of service by flooding the broker with unanswered echo flow frames. The root cause is absent rate-limiting on echo flow response logic in the qpid-broker-plugins-amqp-1-0-protocol plugin. No public exploit code or CISA KEV listing has been identified; the vendor has released a fix in version 10.1.0.
Resource exhaustion in Apache Qpid Broker-J through version 10.0.1 enables authenticated remote attackers to cause denial of service by submitting an unbounded number of AMQP 1.0 transfer frames within a single incoming delivery, with no broker-side enforcement of a per-delivery frame ceiling. The broker's AMQP 1.0 protocol plugin lacks the necessary throttling logic, meaning sustained abuse can exhaust memory and CPU resources and deny service to legitimate messaging clients. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; a vendor-released patch is available in version 10.1.0.
Denial of service in Apache Qpid Broker-J through version 10.0.1 allows authenticated AMQP 1.0 clients to exhaust broker CPU resources by sending crafted disposition frames containing large or illegal delivery-ID ranges. The broker's naive range iteration logic processes these ranges without bounds enforcement, causing excessive CPU consumption that degrades or halts message brokering for all connected clients. No public exploit code and no confirmed active exploitation are known at time of analysis; vendor-released fix 10.1.0 is available.
Excessive heap allocation in Apache Qpid Proton-J's AMQP type parser exposes any network-accessible AMQP endpoint to unauthenticated denial-of-service before an authentication handshake completes. Malformed AMQP frames containing attacker-controlled size or count field values cause the Java library to allocate unbounded memory, leading to JVM heap exhaustion and service crash. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis, but the pre-authentication attack vector and zero-privilege requirement make this a high-priority patch target for any internet-exposed Proton-J deployment.