Search: update-help.com
67 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| High | 7.5 | EPSS 0.3% | High7.5EPSS 0.3%GCVE DatabaseCVE-2025-71128 In the Linux kernel, the following vulnerability has been resolved: erspan: Initialize options_len before referencing options. The struct ip_tunnel_info has a flexible array member named options that is protected by a counted_by(options_len) attribute. The compiler will use this information to enforce runtime bounds checking deployed by FORTIFY_SOURCE string helpers. As laid out in the GCC documentation, the counter must be initialized before the first reference to the flexible array member. After scanning through the files that use struct ip_tunnel_info and also refer to options or options_len, it appears the normal case is to use the ip_tunnel_info_opts_set() helper. Said helper would initialize options_len properly before copying data into options, however in the GRE ERSPAN code a partial update is done, preventing the use of the helper function. Before this change the handling of ERSPAN traffic in GRE tunnels would cause a kernel panic when the kernel is compiled with GCC 15+ and having FORTIFY_SOURCE configured: memcpy: detected buffer overflow: 4 byte write of buffer size 0 Call Trace: <IRQ> __fortify_panic+0xd/0xf erspan_rcv.cold+0x68/0x83 ? ip_route_input_slow+0x816/0x9d0 gre_rcv+0x1b2/0x1c0 gre_rcv+0x8e/0x100 ? raw_v4_input+0x2a0/0x2b0 ip_protocol_deliver_rcu+0x1ea/0x210 ip_local_deliver_finish+0x86/0x110 ip_local_deliver+0x65/0x110 ? ip_rcv_finish_core+0xd6/0x360 ip_rcv+0x186/0x1a0 Reported-at: https://launchpad.net/bugs/2129580 | GCVE Database | ||
| Critical | 9.6 | EPSS 0.4% | CVE-2026-22783dfir-iris iris-web · Unrestricted File Upload Critical9.6EPSS 0.4%CVE Database V5CVE-2026-22783 Iris is a web collaborative platform that helps incident responders share technical details during investigations. Prior to 2.4.24, the DFIR-IRIS datastore file management system has a vulnerability where mass assignment of the file_local_name field combined with path trust in the delete operation enables authenticated users to delete arbitrary filesystem paths. The vulnerability manifests through a three-step attack chain: authenticated users upload a file to the datastore, update the file's file_local_name field to point to an arbitrary filesystem path through mass assignment, then trigger the delete operation which removes the target file without path validation. This vulnerability is fixed in 2.4.24. | CVE Database V5 | ||
| High | 8.4 | EPSS 1.4% | CVE-2026-0830AWS Kiro IDE · OS Command Injection High8.4EPSS 1.4%CVE Database V5CVE-2026-0830 CVE-2026-0830 is a high-severity OS command injection vulnerability in AWS Kiro IDE versions prior to 0.6.18. It arises from improper neutralization of special elements in workspace folder names processed by the Kiro GitLab Merge-Request helper. Opening a maliciously crafted workspace folder could allow an attacker to execute arbitrary OS commands. Users are advised to update to version 0.6.18 or later to mitigate this issue. | CVE Database V5 | ||
| Medium | 4.3 | EPSS 0.2% | Medium4.3EPSS 0.2%CVE Database V5CVE-2025-13657 The HelpDesk contact form plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.5. This is due to missing or incorrect nonce validation on the handle_query_args() function. This makes it possible for unauthenticated attackers to update the plugin's license ID and contact form ID settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. | CVE Database V5 | ||
| –Not rated | – | AlienVault OTX General A multi-stage malware execution chain originating from a ClickFix lure has been discovered, leading to the delivery of infostealing malware like LummaC2 and Rhadamanthys. The campaign utilizes steganography to hide malicious code within PNG images. Two distinct ClickFix lures were observed: a standard 'Human Verification' and a convincing fake Windows Update screen. The execution chain involves mshta.exe, PowerShell, and .NET assemblies, ultimately extracting and injecting shellcode into target processes. The steganographic technique encodes malicious data directly into image pixel data, using specific color channels for payload reconstruction and decryption in memory. This sophisticated approach helps evade signature-based detection and complicates analysis. | AlienVault OTX General | |||
| High | 8.7 | EPSS 14% | CVE-2025-34311IPFire · OS Command Injection High8.7EPSS 14%CVE Database V5CVE-2025-34311 IPFire versions prior to 2.29 (Core Update 198) contain a command injection vulnerability that allows an authenticated attacker to execute arbitrary commands as the user 'nobody' via multiple parameters when creating a Proxy report. When a user creates a Proxy report the application issues an HTTP POST to /cgi-bin/logs.cgi/calamaris.dat and reads the values of DAY_BEGIN, MONTH_BEGIN, YEAR_BEGIN, DAY_END, MONTH_END, YEAR_END, NUM_DOMAINS, PERF_INTERVAL, NUM_CONTENT, HIST_LEVEL, NUM_HOSTS, NUM_URLS, and BYTE_UNIT, which are interpolated directly into the shell invocation of the mkreport helper. Because these parameters are never sanitized for improper characters or constructs, a crafted POST can inject shell metacharacters into one or more fields, causing arbitrary commands to run with the privileges of the 'nobody' user. | CVE Database V5 | ||
| Low | 3.6 | EPSS 0.6% | CVE-2025-27613SUSE · Security update for git Low3.6EPSS 0.6%GCVE DatabaseCVE-2025-27613 A security update for Git addresses multiple critical vulnerabilities including arbitrary writable file creation, arbitrary script execution, arbitrary code execution via protocol injection, and a buffer overflow in the Windows credential helper. These issues affect Gitk, Git GUI, and the credential helper components. The update to version 2.51.0 resolves these vulnerabilities. | GCVE Database | ||
| Medium | 4.0 | EPSS 0.8% | CVE-2025-48432Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update Medium4.0EPSS 0.8%GCVE DatabaseCVE-2025-48432 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-controller: Django SQL injection in FilteredRelation column aliases (CVE-2025-57833) * automation-controller: Django Path Injection Vulnerability (CVE-2025-48432) * python3.11-django: Django SQL injection in FilteredRelation column aliases (CVE-2025-57833) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Increased gateway control plane authorization performance to reduce or eliminate sporadic request errors (503, 504, 403) (AAP-53468) * Fixed a bug where the gateway does not generate the necessary metadata for the UI to render "Settings" > "Platform Gateway" when the accessing user is an auditor rather than an admin (AAP-53279) * If the GRPC server can not connect to the database it will now return a 503 to envoy instead of a 403 (AAP-51931) * Altered the help text for the setting ALLOW_OAUTH2_FOR_EXTERNAL_USERS (AAP-51886) * Fixed improperly formatted error message in SAML authenticator when passing invalid security settings. The error will now properly show the invalid fields and will also indicate what valid field values are (AAP-51705) * Improved debug logging of authenticator map processing, reasoning and results for clarity (AAP-51639) * Fixed an issue with authenticator maps not properly evaluating attribute 'in' conditions (AAP-51638) * When logging in with SAML authentication, user's groups will be correctly read from configured attribute instead of expecting groups to always be in "Group" attribute (AAP-51503) * Added scrolling to multiselect dialogs to make pagination visible for users (AAP-52209) * Fixed an issue that did not allow a user to save Schedule for Workflow job template when Limit has Prompt on Launch was enabled (AAP-49794) * automation-gateway has been updated to 2.5.20250924 * python3.11-django-ansible-base has been updated to 2.5.20250924 Automation controller * Galaxy credentials can now be created and edited without the need to specify an organization (AAP-52197) * Fixed a path injection vulnerability in Django so that internal HTTP response logging escapes request.path and remote attackers can't manipulate log output via crafted URLs (AAP-51443) * The export command works through the controller collection or with awxkit along when the correct environment variable is provided (AAP-49452) * Fixed double escaped quotes in api/v2/jobs/{id}/stdout/?format=txt (AAP-49077) * The export module in the collection now honors the CONTROLLER_OPTIONAL_API_URLPATTERN_PREFIX environment variable, fixing a bug where exports did not work on deployments using the platform gateway (AAP-39265) * automation-controller has been updated to 4.6.20 Automation hub * Added the GALAXY_API_SPEC_REQUIRE_AUTHENTICATION setting (defaults to false), which restricts access to the OpenAPI specification to authenticated users only (AAP-53578) * automation-hub has been updated to 4.10.8 * python3.11-galaxy-ng has been updated to 4.10.8 Container-based Ansible Automation Platform * Disable IPv6 binding on PostgreSQL and Redis services when IPv6 is disabled on the host (AAP-53546) * Fixed the restore and implemented a migration for the controller resource secret key value (AAP-53535) * Uploading ansible collections to Private Automation Hub isn't limited by the API pagination anymore (AAP-53526) * Execute the create_initial_data EDA command during restore (AAP-53382) * Fix an issue with the Private Automation Hub task name using quotes (AAP-53307) * Fixed a path issue for custom_ca_cert when checking postgres connection and version during preflight (AAP-53213) * Fix PostgreSQL configuration directory creation when TLS is disabled (AAP-52569) * X-Forwarded-For and Real-Ip headers are now added to the Nginx logs (AAP-52562) * containerized installer setup has been updated to 2.5-19 RPM-based Ansible Automation Platform * Fixed an issue where redis_mode=standalone and the Redis group were defined at the same time (AAP-53560) * Fixed an issue with EDA restores where database credentials were not updated for event stream (AAP-53529) * Fixed an issue where redis node list could not be created on EDA/gateway nodes which were not part of the redis group (AAP-53528) * Fixed an issue where backup was failing when the deployment had more than 1 EDA node without eda_node_type defined (AAP-528 | GCVE Database | ||
| Medium | 5.5 | EPSS 0.2% | Medium5.5EPSS 0.2%GCVE DatabaseCVE-2025-39807 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add error handling for old state CRTC in atomic_disable Introduce error handling to address an issue where, after a hotplug event, the cursor continues to update. This situation can lead to a kernel panic due to accessing the NULL `old_state->crtc`. E,g. Unable to handle kernel NULL pointer dereference at virtual address Call trace: mtk_crtc_plane_disable+0x24/0x140 mtk_plane_atomic_update+0x8c/0xa8 drm_atomic_helper_commit_planes+0x114/0x2c8 drm_atomic_helper_commit_tail_rpm+0x4c/0x158 commit_tail+0xa0/0x168 drm_atomic_helper_commit+0x110/0x120 drm_atomic_commit+0x8c/0xe0 drm_atomic_helper_update_plane+0xd4/0x128 __setplane_atomic+0xcc/0x110 drm_mode_cursor_common+0x250/0x440 drm_mode_cursor_ioctl+0x44/0x70 drm_ioctl+0x264/0x5d8 __arm64_sys_ioctl+0xd8/0x510 invoke_syscall+0x6c/0xe0 do_el0_svc+0x68/0xe8 el0_svc+0x34/0x60 el0t_64_sync_handler+0x1c/0xf8 el0t_64_sync+0x180/0x188 Adding NULL pointer checks to ensure stability by preventing operations on an invalid CRTC state. EPSS 0.2%Vulnerability | GCVE Database | ||
| High | 8.8 | EPSS 0.6% | CVE-2025-59145colorjs color-name · Embedded Malicious Code High8.8EPSS 0.6%CVE Database V5CVE-2025-59145 color-name is a JSON with CSS color names. On 8 September 2025, an npm publishing account for color-name was taken over after a phishing attack. Version 2.0.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 2.0.2. | CVE Database V5 | ||
| High | 8.8 | EPSS 0.4% | CVE-2025-59331Qix- node-is-arrayish · Embedded Malicious Code High8.8EPSS 0.4%CVE Database V5CVE-2025-59331 is-arrayish checks if an object can be used like an Array. On 8 September 2025, an npm publishing account for is-arrayish was taken over after a phishing attack. Version 0.3.3 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 0.3.4. | CVE Database V5 | ||
| High | 8.8 | EPSS 0.4% | CVE-2025-59330Qix- node-error-ex · Embedded Malicious Code High8.8EPSS 0.4%CVE Database V5CVE-2025-59330 error-ex allows error subclassing and stack customization. On 8 September 2025, an npm publishing account for error-ex was taken over after a phishing attack. Version 1.3.3 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 1.3.4. | CVE Database V5 | ||
| High | 8.8 | EPSS 0.4% | CVE-2025-59162Qix- color-convert · Embedded Malicious Code High8.8EPSS 0.4%CVE Database V5CVE-2025-59162 color-convert provides plain color conversion functions in JavaScript. On 8 September 2025, the npm publishing account for color-convert was taken over after a phishing attack. Version 3.1.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 3.1.2. | CVE Database V5 | ||
| High | 8.8 | EPSS 0.4% | CVE-2025-59143Qix- color · Embedded Malicious Code High8.8EPSS 0.4%CVE Database V5CVE-2025-59143 color is a Javascript color conversion and manipulation library. On 8 September 2025, the npm publishing account for color was taken over after a phishing attack. Version 5.0.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issues has been resolved in 5.0.2. | CVE Database V5 | ||
| High | 8.8 | EPSS 0.4% | CVE-2025-59141Qix- node-simple-swizzle · Embedded Malicious Code High8.8EPSS 0.4%CVE Database V5CVE-2025-59141 simple-swizzle swizzles function arguments. On 8 September 2025, the npm publishing account for simple-swizzle was taken over after a phishing attack. Version 0.2.3 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc.are not affected. If the package was used in a browser context (e.g.a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask.npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 0.2.4. | CVE Database V5 | ||
| Medium | 5.5 | EPSS 0.2% | Medium5.5EPSS 0.2%GCVE DatabaseCVE-2025-38427 In the Linux kernel, the following vulnerability has been resolved: video: screen_info: Relocate framebuffers behind PCI bridges Apply PCI host-bridge window offsets to screen_info framebuffers. Fixes invalid access to I/O memory. Resources behind a PCI host bridge can be relocated by a certain offset in the kernel's CPU address range used for I/O. The framebuffer memory range stored in screen_info refers to the CPU addresses as seen during boot (where the offset is 0). During boot up, firmware may assign a different memory offset to the PCI host bridge and thereby relocating the framebuffer address of the PCI graphics device as seen by the kernel. The information in screen_info must be updated as well. The helper pcibios_bus_to_resource() performs the relocation of the screen_info's framebuffer resource (given in PCI bus addresses). The result matches the I/O-memory resource of the PCI graphics device (given in CPU addresses). As before, we store away the information necessary to later update the information in screen_info itself. Commit 78aa89d1dfba ("firmware/sysfb: Update screen_info for relocated EFI framebuffers") added the code for updating screen_info. It is based on similar functionality that pre-existed in efifb. Efifb uses a pointer to the PCI resource, while the newer code does a memcpy of the region. Hence efifb sees any updates to the PCI resource and avoids the issue. v3: - Only use struct pci_bus_region for PCI bus addresses (Bjorn) - Clarify address semantics in commit messages and comments (Bjorn) v2: - Fixed tags (Takashi, Ivan) - Updated information on efifb | GCVE Database | ||
| Medium | 6.2 | EPSS 0.6% | Medium6.2EPSS 0.6%GCVE DatabaseCVE-2025-27789 Babel versions prior to 7.26.10 and 8.0.0-alpha.17 generate code with a polyfill for the .replace method that exhibits quadratic complexity on certain replacement pattern strings when compiling regular expression named capturing groups. This vulnerability can lead to denial of service if untrusted input is used as the replacement string in .replace. The issue is fixed in @babel/helpers and @babel/runtime versions 7.26.10 and 8.0.0-alpha.17. Users must update these dependencies and recompile their code to mitigate the vulnerability. No known workarounds exist. EPSS 0.6%Vulnerability | GCVE Database | ||
| High | 8.1 | KEVEPSS 21% | CVE-2025-23209craftcms cms · Code Injection High8.1KEVEPSS 21%CVE Database V5CVE-2025-23209 Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. This is an remote code execution (RCE) vulnerability that affects Craft 4 and 5 installs where your security key has already been compromised. Anyone running an unpatched version of Craft with a compromised security key is affected. This vulnerability has been patched in Craft 5.5.8 and 4.13.8. Users who cannot update to a patched version, should rotate their security keys and ensure their privacy to help migitgate the issue. | CVE Database V5 | ||
| Medium | – | EPSS 0.3% | CVE-2024-36472Red Hat Security Advisory: gnome-shell security update MediumEPSS 0.3%GCVE DatabaseCVE-2024-36472 A security vulnerability (CVE-2024-36472) in GNOME Shell's portal helper component allows for code execution. GNOME Shell is the desktop compositing manager responsible for core interface functions such as window switching and application launching. Red Hat has issued a security update addressing this moderate severity issue in Red Hat Enterprise Linux 9.4 Extended Update Support. | GCVE Database |
Page 4 of 5 · 1 duplicate CVE record merged