CVE-2026-102497 is a denial of service vulnerability in Apache XMLSchema's xmlschema-walker component. The walker does not detect cycles in type derivation, substitution groups, model groups, or attribute groups, which can cause recursive stack overflow. This issue is fixed in Apache XMLSchema version 2.3.3. Users running versions prior to 2.3.3 are vulnerable to this denial of service attack.
Apache XMLSchema versions prior to 2.3.3 contain a vulnerability where deeply nested schema structures can cause a stack overflow during parsing, leading to denial of service. This issue is fixed in version 2.3.3.
Apache XMLSchema versions before 2.3.3 contain a vulnerability where schema imports and includes can be nested without limit, leading to stack overflow during parsing. This results in a denial of service condition. The issue is fixed in version 2.3.3.
The Apache Airflow Teradata provider's compute-cluster example Dag declared every one of its Dag Params as unconstrained free text and templated them straight into the compute-cluster operators, which interpolate those values into Teradata DDL. A user who is permitted to trigger that Dag - a lower-trust role than the Dag author, and one that needs no Teradata credentials of its own - could therefore supply SQL fragments that execute under the connection the task runs as, and could additionally redirect the task at any other connection defined in the deployment, because the connection id was itself a free-text Param. Only deployments that run this example Dag, or a Dag copied from it, are affected; the provider's operator code is unchanged. Users of apache-airflow-providers-teradata are recommended to upgrade to version 3.7.0 or later, whose example constrains the Params to validated identifiers and a closed value set and removes connection selection and free-form option strings from trigger-time input. Upgrading does not change a Dag already copied from the example; users who copied it should apply the same constraints to their copy.
Apache Airflow's Snowflake provider did not validate the connection's `account` and `region` fields before interpolating them into request URLs. The SQL API endpoint is built as `https://{account}.snowflakecomputing.com/api/v2/statements`, so an `account` value containing `/`, `?` or `#` demotes the intended domain to a path, query or fragment and leaves the attacker in control of the request host.
The provider sends that request with an `Authorization: Bearer` header carrying a JWT minted from the connection's private key, or the configured OAuth or programmatic access token. A user who can edit the Snowflake connection but cannot read its secrets — Airflow gives connection-configuration users write-only access to stored credentials, and a `private_key_file` lives on the worker rather than in the connection — can therefore cause a valid token for the account to be delivered to a host of their choosing and replay it against the genuine Snowflake endpoint. No Dag-authoring ability is required: the attacker edits the connection and waits for an existing Dag to use it. The same unvalidated value was also used to build the OAuth token-request URL and the Cortex Agent base URL.
Affects deployments where Snowflake connections are editable by users who are not trusted with the connection's credentials. Users are advised to upgrade to `apache-airflow-providers-snowflake` `6.18.0` or later, which rejects `account` and `region` values containing anything other than letters, digits, `.`, `_` and `-` in every URL the provider builds from them.
Apache Airflow's Teradata provider versions before 3.7.0 embed cloud storage credentials directly into SQL statements, which are then logged in Airflow task logs and Teradata's query logs. This exposure occurs when using the S3ToTeradataOperator or AzureBlobStorageToTeradataOperator against private buckets without a configured Teradata authorization object. The credentials appear in plaintext in Airflow logs and Teradata's DBQL query logs, posing a risk of credential leakage. Upgrading to version 3.7.0 or later prevents credentials from appearing in Airflow logs but does not remove them from Teradata's logs. Users should configure a Teradata authorization object and rotate exposed credentials.
CVE-2026-81914 is a medium severity vulnerability in the Apache Airflow Google provider where Google Drive search queries improperly handle special characters in file and folder names. Specifically, names containing apostrophes are not escaped, allowing an attacker controlling these names to inject additional clauses into the query. This can cause the system to select attacker-controlled files or folders during upload or download operations, potentially redirecting data flows. The issue affects versions prior to 22.6.0. Upgrading to version 22.6.0 or later mitigates the vulnerability by properly escaping special characters in queries.
Apache Karaf versions before 4.4.12 have a vulnerability in the JMX MBeanServer access control. The KarafMBeanServerGuard enforces role-based access control (RBAC) on certain MBean operations but omits lifecycle operations like createMBean, registerMBean, and unregisterMBean from checks. This allows any authenticated JMX user, including those with minimal 'viewer' roles, to instantiate and remove arbitrary MBeans without authorization. Exploiting this, an attacker can instantiate the standard JDK MLet MBean to load and execute attacker-controlled classes remotely, leading to remote code execution. The issue is fixed by adding these lifecycle operations to the guarded list and restricting them to the 'admin' role in Apache Karaf 4.4.12 and later.
Apache Karaf versions before 4.4.12 have a security vulnerability where the shell/SSH command ACL enforcement fails open for unmatched commands, allowing any authenticated user to execute certain commands like config:install. This command can fetch and overwrite critical configuration files, potentially leading to privilege escalation. The default configuration does not enforce strict role checks for unmatched commands, increasing risk. Mitigation involves explicitly restricting the install command to admin roles or enabling a setting to fail unmatched commands closed.
CVE-2026-91048 is a critical privilege escalation vulnerability in Apache Karaf affecting versions prior to 4.4.12. The jdbc and jms shell commands lack proper ACL configuration, allowing any authenticated user, including those with only viewer role, to execute all jdbc:* and jms:* commands. This flaw enables an attacker to store a fully controlled JDBC URL that can trigger arbitrary code execution via JDBC driver URL parameters, bypassing admin role restrictions.
CVE-2026-91012 is a critical directory traversal vulnerability in Apache Karaf's configuration management component. It allows users with the 'manager' role to write configuration files to arbitrary locations writable by the Karaf process, bypassing intended access controls. This can lead to privilege escalation by modifying files reserved for the 'admin' role, enabling takeover of the container. The vulnerability arises from insufficient validation of file paths derived from user-supplied input in ConfigRepositoryImpl.update() and createFactoryConfiguration().
CVE-2026-91006 is an OS command injection vulnerability in Apache Karaf's instance-management service. The vulnerability arises because the javaOpts parameter is concatenated into a shell command without proper quoting, allowing shell metacharacters to be interpreted by the OS shell. This can lead to arbitrary command execution with the privileges of the Karaf process user. The flaw is reachable via several Karaf shell commands and JMX operations related to instance management. Mitigations include restricting access to these commands and treating javaOpts as untrusted input unless from fully trusted operators.
CVE-2026-90979 is an LDAP injection vulnerability in Apache Karaf affecting versions before 4.4.12. The issue arises from improper escaping of special characters in LDAP search filters constructed by LDAPCache and LDAPBackingEngine. This can allow crafted input to alter LDAP queries, potentially causing unauthorized role assignments or incorrect user account resolution. The vulnerability is exploitable through certain authentication modules that do not apply proper escaping, such as GSSAPILdapLoginModule and LDAPBackingEngine listRoles. The vulnerability has a high severity score of 7.3.
Improper neutralization of input in Apache Roller 6.1.5 allows an anonymous remote attacker to store a crafted comment-author URL that can execute script in the session of a weblog moderator or global administrator when the comment management page is viewed. This affects sites that permit comments on at least one weblog and whose moderator subsequently reviews the submitted comment; no non-default server setting is required. Users are recommended to upgrade to Apache Roller 6.1.6 or later.
CVE-2026-82379 is an authentication bypass vulnerability in Apache Roller 6.1.5 affecting installations that enable the non-default AtomPub API with WSSE authentication and plaintext-compatible password storage. The flaw allows an attacker who captures a valid WSSE digest authentication header to replay it and gain the victim's AtomPub authority due to lack of nonce uniqueness and timestamp freshness enforcement. Apache Roller 6.1.6 and later remove WSSE as an AtomPub authentication method, mitigating this issue.
Cross-Site Request Forgery (CSRF) in Apache Roller 6.1.5 allows a remote attacker to cause a logged-in user to perform state-changing actions under the victim's authority, because the CSRF validation filters accept a request that does not submit the required salt token, validating instead against a value the server itself generated for the request. No optional feature or non-default configuration is required; any logged-in author or administrator is affected when induced to visit a crafted page. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which validates only the submitted salt and applies the same check to multipart forms.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Apache Roller 6.1.5 allows a user with authoring rights on a weblog to store crafted content that is later written into the authoring UI's JavaScript string literals and markup sinks without proper encoding, causing the stored script to execute in another author's or administrator's browser. No optional feature or non-default configuration is required; this affects weblogs with multiple authors or administrators who are not mutually trusted. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which moves those values out of JavaScript literals and writes them as text.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Apache Roller 6.1.5 allows a remote attacker to perform reflected cross-site scripting against a visitor to a weblog using the bundled frontpage theme, by supplying a crafted blog-directory parameter that the directory page reflects without proper escaping. This affects only weblogs that use the bundled frontpage theme, and a victim must follow a crafted link for the script to execute. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which validates and contextually escapes the reflected parameter.
Missing Authentication for Critical Function in Apache Roller 6.1.5 allows an unauthenticated remote attacker to persistently change a site-global configuration value (the frontpage weblog selection) on any installed instance, because the setup action remains anonymously reachable after installation and persists configuration without an authorization check. No optional feature or non-default configuration is required; the result can redirect or break the site's public frontpage, with administrative recovery available. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which restricts the write to global administrators.
Apache Roller 6.1.5 contains a critical deserialization vulnerability in its XML-RPC endpoint that allows unauthenticated remote attackers to cause deserialization of attacker-controlled data. This occurs because the endpoint accepts vendor extension types that are deserialized before authentication, even if the XML-RPC feature is disabled globally. This flaw can lead to remote code execution. Upgrading to Apache Roller 6.1.6 or later mitigates the issue by disabling these extension types and rejecting requests when XML-RPC is disabled.