A heap-based buffer overflow vulnerability exists in Apache HTTP Server versions from 2.4.0 through 2.4.67, related to interactions with malicious backend servers and the ProxyPassReverseCookie* directive. This vulnerability can cause a denial of service due to server crashes. The issue is fixed in Apache HTTP Server version 2.4.68.
CVE-2026-44186 is a high-severity vulnerability in the Apache HTTP Server's mod_proxy_ftp module that causes an infinite loop due to an unreachable exit condition. This affects versions from 2.4.0 through 2.4.67. The vulnerability can be triggered by an attacker-controlled backend FTP server. Users are advised to upgrade to version 2.4.68, which addresses this issue.
CVE-2026-29170 is a cross-site scripting (XSS) vulnerability in Apache HTTP Server's mod_proxy_ftp module affecting versions 2.4.67 and earlier. The issue occurs during HTML directory list generation when listing FTP directory contents via forward or reverse proxy. This vulnerability allows an attacker to inject malicious scripts that could be executed in the context of the user's browser. The Apache Software Foundation recommends upgrading to version 2.4.68 to address this vulnerability.
A critical Use After Free vulnerability (CWE-416) exists in the mod_ldap module of Apache HTTP Server affecting per-directory configuration. This vulnerability impacts Apache HTTP Server versions from 2.4.0 through 2.4.67. It allows for potential complete compromise of confidentiality, integrity, and availability. Users are advised to upgrade to version 2.4.68, which addresses this vulnerability.
## Summary
The iOS implementation of `cordova-plugin-inappbrowser` passes the `id` field from a `WKScriptMessage` body to `commandDelegate sendPluginResult:callbackId:` with no format validation (`CDVWKInAppBrowser.m:560–574`). Any web content loaded inside the InAppBrowser can fire any pending Cordova callback in the host app by posting a message whose `id` field is a guessable or enumerated callback identifier. An attack abusing this weakness must be tailored to the specific plugins and callback IDs the host app uses. Though an attacker with knowledge of common Cordova plugin configurations could craft reusable payloads targeting widely-adopted plugins.
## Impact
An unauthenticated remote attacker who controls content displayed in the InAppBrowser — via a URL the app opens (OAuth redirect, marketing link, deep-link target) or a network interception — can call `window.webkit.messageHandlers.cordova_iab.postMessage({id: '<victim-callback-id>', d: '...'})` to fire callbacks belonging to any other installed Cordova plugin (Camera, Contacts, File, Geolocation). Cordova callback IDs follow the predictable format `<PluginName><sequential-integer>`, making enumeration feasible. Successful exploitation allows the attacker to spoof plugin results across trust boundaries — for example, injecting a forged camera approval, a fabricated contacts list, or a crafted file-read response.
This issue affects Cordova Plugin InAppBrowser: from 3.1.0 through 6.0.0.
Users are recommended to upgrade to version 6.0.1, which fixes the issue.
A critical deserialization vulnerability (CWE-502) exists in Apache Fory fory-core Java SDK versions before 1.1.0. It allows remote attackers to bypass security checks and invoke dangerous Java serialization hooks via crafted serialized data. Upgrading to version 1.1.0 or later addresses this issue.
ZDRES-232: resolveProxyClass Not Overridden - acceptMatchers Filter Bypass via java.lang.reflect.Proxy Assessment: Fully addressed. When the serialised stream contains a TC_PROXYCLASSDESC (the marker for a java.lang.reflect.Proxy ), JDK’s ObjectInputStream.readProxyDesc() is dispatched. JDK then calls the default ObjectInputStream.resolveProxyClass(interfaces) implementation, which performs Class.forName(intf, false, latestUserDefinedLoader()) for EACH interface name and constructs the proxy class — bypassing the accepted classes list . ZDRES-233: Class.forName(name, initialize=true, classLoader) in readClassDescriptor Triggers Static Initialiser of Allow-Listed Classes Assessment: Fully addressed. For ANY class on the allow-list, deserialising a stream that names it triggers the class’s (static initialiser) BEFORE any instance is constructed. This means an attacker who supplies a class name on the allow-list (e.g., the developer wrote accept(“com.myapp.*") , attacker supplies com.myapp.SomeClass ) causes <clinit> of SomeClass — and many real-world classes have side-effecting static initialisers Both issues have been fixed.
Apache Calcite versions from 1.5.0 up to but not including 1.42 contain a vulnerability involving unsafe reflection, where externally-controlled input is used to select classes or code. This can lead to limited confidentiality and integrity impacts. The issue is fixed in version 1.42.
An improper authorization vulnerability has been identified in Apache Kafka.
The implementation of the CONSUMER_GROUP_DESCRIBE (69) API validates the DESCRIBE operation on the GROUP resource instead of the READ operation that documented in the official kafka documentation and the KIP-848. This discrepancy can result in misconfigured Access Control Lists (ACLs) and unintended security postures, like granting READ permission to users who should not be able to join/sync groups, or allowing users without READ permission (but with DESCRIBE permission) to access sensitive group metadata.
The correct permission for CONSUMER_GROUP_DESCRIBE API is DESCRIBE GROUP so the current implementation is correct. However, the kafka documentation as well as the KIP-848 will be updated to reflect the correct permission. We advise the Kafka users to review existing group ACLs to ensure the principle of least privilege.
Server-Side Request Forgery (SSRF) in the UrlImageConverter component of Apache Fesod (Incubating) fesod-sheet before 2.0.2-incubating allows attackers to cause outbound network requests to internal or otherwise restricted resources via a user-supplied image URL. Users are recommended to upgrade to version 2.0.2-incubating, which fixes this issue.
Apache Airflow's scheduler-side deadline-reference decoder (`SerializedCustomReference.deserialize_reference`) imported and dispatched arbitrary class paths drawn from DAG-author-controlled serialized state without an allowlist or plugin-registry gate. A DAG author whose code reaches the scheduler — the default on single-host deployments where the DAG bundle is importable from the scheduler process — could embed a custom `DeadlineReference` whose serialized form named an attacker-controlled module path, causing the scheduler to `import_string(...)` and instantiate that class with a live SQLAlchemy session attached. Affects deployments where DAG-author code is less trusted than the scheduler process. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Hardcoded credentials in the Basic Authentication setup tool (bin/solr auth enable) in Apache Solr versions 9.4.0 through 9.10.1 and 10.0.0 allows a remote attacker to gain full administrative access to the cluster via publicly known default credentials installed silently alongside the user-specified account.
As an immediate workaround without upgrading, delete the template users (superadmin, admin, search, index) from security.json or change their passwords.
The future, not yet released, versions 9.11.0 and 10.1.0 will not be vulnerable, and it will be enough to upgrade to solve the issue.
Not affected:
* Clusters where bin/solr auth enable was not used to bootstrap BasicAuth
* Clusters where template users have been assigned strong passwords after bootstrap
Incomplete authorization by Apache ActiveMQ server before versions v6.2.6 and v5.19.7 allows authenticated connections to remove existing destinations with proper permissions. This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version v6.2.6 or v5.19.7, which fixes the issue.
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. Non-parenthesized discovery wrappers such as `masterslave:vm://...,...` and `static:vm://...` incorrectly pass validation allowing bypass of fix in CVE-2026-34197. Original description from CVE-2026-34197. Apache ActiveMQ exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String) and BrokerService.addConnector(String). An authenticated attacker can invoke these operations with a crafted discovery UR that triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String). An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter using the "masterslave:// " URL which can allow loading a Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.
A path traversal vulnerability (CWE-22) exists in Apache MINA SSHD's sshd-git bundle, allowing authenticated SSH users to access git repositories outside the configured server root directory due to insufficient path validation in git-upload-pack, git-receive-pack, and related operations. This affects applications using org.apache.sshd:sshd-git. The issue is fixed in Apache MINA SSHD version 2.18.0 and in milestone 3.0.0-M4. Users should upgrade to these versions to mitigate the vulnerability. Additional security controls beyond file system permissions are recommended for professional git servers.
Apache Fluss versions prior to 0.9.1 configure the Netty LengthFieldBasedFrameDecoder with Integer.MAX_VALUE as the maximum frame length, allowing unauthenticated remote attackers to exhaust JVM heap memory on TabletServer and CoordinatorServer by sending specially crafted frame headers, resulting in denial of service.
This issue affects Apache Fluss (incubating): 0.8.0 and 0.9.0.
Users are recommended to upgrade to version 0.9.1, which fixes the issue.
CVE-2026-40861 is a medium severity vulnerability in Apache Airflow prior to version 3.2.2. It involves improper link resolution before file access, allowing a DAG author to cause the FileTaskHandler to read or overwrite arbitrary files outside the intended log directory. This occurs when the worker log folder is shared with the API server. The vulnerability can lead to sensitive file disclosure but does not affect availability or integrity directly.
CVE-2026-40961 is a high-severity open redirect vulnerability in Apache Airflow version 3.0.0. It allows authenticated users to bypass the is_safe_url check in the login redirect route, enabling redirection from a trusted Airflow domain to attacker-controlled sites. This can lead to phishing or other malicious redirection attacks. Users are advised to upgrade to Apache Airflow 3.2.2 or later. As a defense-in-depth measure, operators can use a reverse proxy to strip off-domain next= query parameters before they reach the login endpoint.
Apache Airflow version 3.0.0 has an improper authorization vulnerability in the structure_data endpoint of its UI. This flaw allows authenticated users with read access to one DAG to enumerate linked DAG IDs and dependency metadata for other DAGs they are not authorized to access. This issue affects deployments that rely on per-DAG read scoping to maintain privacy of DAG dependency topology across teams. Users are advised to upgrade to Apache Airflow 3.2.2 or later to address this issue.