Export limit exceeded: 112696 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (112696 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-86829 | 1 Apache | 1 Airflow | 2026-11-15 | 8.8 High |
| Apache Airflow's scheduler fully deserializes XCom values written by task code while evaluating task dependencies. A Dag author, who controls what a task writes to XCom, therefore controls data that is deserialized inside the scheduler process - a context the Airflow security model reserves for code installed by the Deployment Manager, above the worker-scoped execution capability a Dag author is documented to have. Deployments that treat Dag authors as less trusted than Deployment Managers are affected, and the scheduler must be evaluating a task dependency that reads a task-written XCom value. Users of apache-airflow are recommended to upgrade to version 3.4.0 or later, which restricts dependency evaluation to primitive XCom values. | ||||
| CVE-2026-40913 | 1 Apache | 1 Airflow | 2026-11-15 | 8.2 High |
| Apache Airflow's public Import Errors API returns the raw parse-failure stack trace to any user with the `ImportError.can_read` permission when the failing file has no registered DAG. This happens when a file fails to parse before any DAG is defined, or when all of its previously registered DAGs are removed but the parse error remains. Users who should not see that file's details can read stack traces that may expose file paths and code. Users are advised to upgrade to Apache Airflow 3.4.0 or later, which restricts these stack traces to users with the new `IMPORT_ERRORS_ALL` permission. | ||||
| CVE-2026-82440 | 1 Apache | 1 Storm Nimbus | 2026-11-15 | 8.1 High |
| Description Nimbus instantiates the class named by a topology's `topology.scheduler.strategy` when scheduling it. The allowlist intended to constrain that choice, `nimbus.scheduler.strategy.class.whitelist`, was treated as "allow any class" when unset, and it had no entry in the shipped `defaults.yaml`, so unset was the shipped state. An authenticated submitter could therefore cause Nimbus to instantiate any class on the Nimbus classpath that has a no-argument constructor. Storm's own production artifacts contain classes with side effects suitable for this: instantiating `org.apache.storm.testing.InProcessZookeeper` starts a ZooKeeper server with its own threads and sockets and nothing closes it, and `org.apache.storm.LocalCluster` behaves similarly. Repeated submissions therefore consume threads, sockets and memory in the most privileged daemon in the cluster. Mitigation Upgrade to 3.1.0, where an unset allowlist means the strategies shipped with Storm rather than any class. Note that this is a behaviour change: a cluster running an out-of-tree scheduler strategy without an explicit allowlist will have those topologies refused until the class is added to `nimbus.scheduler.strategy.class.whitelist`. The rejection message names the refused class and the configuration key. Users who cannot upgrade immediately should set `nimbus.scheduler.strategy.class.whitelist` explicitly to the strategies they intend to permit. | ||||
| CVE-2026-82436 | 1 Apache | 1 Storm Client | 2026-11-15 | 8.8 High |
| Description `DefaultStateSerializer`, used to persist and restore stateful bolt checkpoints, configured Kryo with class registration disabled and an instantiation strategy that constructs objects without invoking their constructors, then deserialized whatever bytes the state store returned. A party able to write to the topology's keyspace in the state store, for example a co-tenant of a shared Redis instance or anyone with network access to it, could therefore place a serialized object graph that executes code inside the worker JVM when the state is restored. This requires the Redis-backed state provider, which is not the default. Write access to a state-store key is a data-plane privilege; code execution in the worker JVM is not, so the two are not equivalent. Mitigation Upgrade to 3.1.0, where the state serializer requires registered classes. Note that this is a behaviour change for existing state: checkpoints written by an affected version may fail to restore, and a migration step may be required. Users who cannot upgrade immediately should restrict network and credential access to the state store to the cluster itself. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm. | ||||
| CVE-2026-123770 | 1 Apache | 1 Apache Axis2/java | 2026-11-15 | 7.5 High |
| Allocation of Resources Without Limits or Throttling vulnerability in Apache Axis2/Java. The multipart/form-data and application/x-www-form-urlencoded message builders read the request body directly from the transport stream with no size limit, so the servlet container's post-size limit did not apply, and multipart temporary files were not deleted. An unauthenticated caller could exhaust memory or disk. Version 2.0.2 bounds these bodies with configurable limits and deletes temporary files. This issue affects Apache Axis2/Java: through 2.0.1. Users are recommended to upgrade to version 2.0.2, which fixes the issue. | ||||
| CVE-2026-107245 | 1 Versa | 1 Vos | 2026-11-15 | 7.5 High |
| Versa has confirmed a buffer overflow vulnerability in the IPsec implementation on VOS, aka Versa FlexVNF. Buffer Overflow Vulnerability Description When a maliciously crafted IKE Auth packet is sent to VOS, the vsmd process crashes, thereby resulting in a Denial of Service. An attacker can create a Denial-of-Service attack on the VOS appliances by crafting a malicious IKE Auth packet and sending it to the WAN interfaces on the VOS. During the IKE Authentication phase, if the IKE SA negotiation fails, and the size of the Remote ID is larger than the buffer size used to process the Remote ID, it will result in a crash of the vsmd process on the VOS appliance. What is impacted? VOS nodes configured with IPsec VPN profiles of type controller-staging-sdwan or remote-access-server using a WAN interface as the IPsec endpoint are vulnerable. (IPsec profiles configured with an overlay interface as the IPsec endpoint are not affected.) This configuration typically applies to all Controllers, Hub Controllers, and SSE Gateways. Additionally, site-to-site VPN profiles configured without a peer IP address, hostname, or FQDN are also vulnerable. What is not impacted? The VOS nodes listed above are not vulnerable if they are not accessible from the Internet. | ||||
| CVE-2026-125087 | 1 Michael-a-kuykendall | 1 Shimmy | 2026-11-15 | 7.3 High |
| A vulnerability was found in Michael-A-Kuykendall Shimmy up to 2.6.4. The affected element is an unknown function of the file src/server.rs of the component Inference API. Performing a manipulation results in missing authentication. The attack is possible to be carried out remotely. Upgrading to version 2.6.5 is sufficient to fix this issue. The patch is named 3f2ee748c02eeb229987913fe289a2ed9a24595d. You should upgrade the affected component. | ||||
| CVE-2026-120513 | 2026-11-15 | 8.2 High | ||
| The Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI plugin for WordPress is vulnerable to file deletion due to insufficient file path validation in the remove_csv_file_after_email_send function in all versions up to, and including, 3.6.2 This makes it possible for unauthenticated attackers to delete files within the wp-content/uploads directory on the server, which can lead to loss of uploaded content. On hardened Apache configurations, deletion of uploads/.htaccess can re-enable PHP execution inside the uploads directory. This attack is only possible when the Save-and-Continue addon is active (EVF_SAVE_AND_CONTINUE_VERSION is defined) and the 'Disable storing entry information' setting is enabled on the target form. Escaping the uploads directory and deleting files in the site root can be possible under rare circumstances. | ||||
| CVE-2026-4762 | 1 Axis Communications Ab | 1 Axis Camera Station Pro | 2026-11-15 | 8.8 High |
| A vulnerability to perform a privilege escalation attack on the server as a non-admin user. | ||||
| CVE-2026-8372 | 1 Axis Communications Ab | 1 Axis Camera Station Pro | 2026-11-15 | 8.8 High |
| A vulnerability that could allow an attacker to gain unauthorized access. | ||||
| CVE-2026-12389 | 1 Axis Communications Ab | 1 Axis Camera Station Pro | 2026-11-15 | 8.4 High |
| A vulnerability that could lead to a high privileged authenticated user performing a remote code execution attack. | ||||
| CVE-2026-12963 | 1 Axis Communications Ab | 2 Axis Camera Station, Axis Camera Station Pro | 2026-11-15 | 7.4 High |
| A vulnerability that could allow a viewer account to gain unauthorized access to network attached storage devices on the server. | ||||
| CVE-2026-12964 | 1 Axis Communications Ab | 1 Axis Camera Station Pro | 2026-11-15 | 8 High |
| A vulnerability allowing for privileged escalation of the viewer account to gain administrator privileges. | ||||
| CVE-2026-12574 | 1 Zohocorp | 1 Ddi Central | 2026-11-15 | 8.1 High |
| Zoho Corporation ManageEngine DDI Central versions 6200 and below are vulnerable to Server-side HTML/JavaScript injection in analytics PDF generation leading to local file disclosure. | ||||
| CVE-2026-12266 | 1 Zohocorp | 1 Ddi Central | 2026-11-15 | 7.6 High |
| Zoho Corporation ManageEngine DDI Central versions 6200 and below are vulnerable to LDAP bind password exposure through insufficiently protected LDAP settings API. | ||||
| CVE-2026-60035 | 3 Helmholz, Mb Connect Line, Mbconnectline | 8 Myrex24v2, Myrex24v2.virtual, Myrex24v2 Firmware and 5 more | 2026-11-15 | 7.2 High |
| A high privileged remote attacker can perform a code injection in the backends network auth function leading to code execution. This can result in a total loss of confidentiality, integrity and availability. | ||||
| CVE-2026-60039 | 3 Helmholz, Mb Connect Line, Mbconnectline | 8 Myrex24v2, Myrex24v2.virtual, Myrex24v2 Firmware and 5 more | 2026-11-15 | 7.2 High |
| A high privileged remote attacker can perform a code injection in the backends backup restore function leading to code execution. This can result in a total loss of confidentiality, integrity and availability. | ||||
| CVE-2026-60040 | 3 Helmholz, Mb Connect Line, Mbconnectline | 8 Myrex24v2, Myrex24v2.virtual, Myrex24v2 Firmware and 5 more | 2026-11-15 | 7.5 High |
| An unauthenticated remote attacker can perform a DoS in the backends backup creation function. This can result in a total loss of availability. | ||||
| CVE-2026-60044 | 3 Helmholz, Mb Connect Line, Mbconnectline | 8 Myrex24v2, Myrex24v2.virtual, Myrex24v2 Firmware and 5 more | 2026-11-15 | 7.5 High |
| The backups created by the application use a weak static password allowing an unauthenticated remote attacker to access their content. This can result in a total loss of confidentiality. | ||||
| CVE-2026-104619 | 1 Packagekit | 1 Packagekit | 2026-11-15 | 7.8 High |
| Untrusted users could roll back security updates when using the PackageKit Zypp Backend before 1.4.1, allowing privilege escalation. | ||||