Search: components.operating
34 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| High | 8.8 | EPSS 0.6% | CVE-2026-6460PostgreSQL · Type Confusion High8.8EPSS 0.6%GCVE DatabaseCVE-2026-6460 A type confusion vulnerability in PostgreSQL allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. This occurs due to inadequate tracking of typed values, leading to stale values appearing in various system components. The flaw can be exploited primarily via ALTER ... SET DATA TYPE commands and other DDL operations. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The vulnerability has a high severity score of 8.8 CVSS v3.1. | GCVE Database | ||
| High | 7.8 | EPSS 0.2% | CVE-2026-124705In Progress® Telerik® UI for .NET MAUI prior to version 16.0.0, an untrusted URL redirection vulnerability in the High7.8EPSS 0.2%GCVE DatabaseCVE-2026-124705 An untrusted URL redirection vulnerability exists in In Progress® Telerik® UI for .NET MAUI versions prior to 16.0.0. This flaw affects the RadRichTextEditor hyperlink handling and the RadPdfViewer link annotation handling components. An unauthenticated attacker can exploit this by crafting a document or PDF containing a link with a non-allowlisted URI scheme, which when opened by a user, can launch arbitrary operating system protocol handlers with attacker-controlled arguments. | GCVE Database | ||
| High | – | EPSS 0.2% | HighEPSS 0.2%GCVE DatabaseCVE-2024-57793 This Red Hat Security Advisory addresses multiple vulnerabilities in the Linux kernel packages, which form the core of the operating system. The update includes fixes for a wide range of security issues such as use-after-free, buffer overflows, integer overflows, race conditions, and denial of service vulnerabilities across various kernel subsystems including virtualization, networking, Bluetooth, USB, and file systems. The advisory covers numerous CVEs from 2024 through 2026, indicating ongoing kernel security improvements. The update is rated as important by Red Hat Product Security and applies to Red Hat Enterprise Linux 10 and its components. | GCVE Database | ||
| High | 7.1 | EPSS 0.2% | High7.1EPSS 0.2%GCVE Database CVE-2026-44382 is an out-of-bounds read vulnerability in some Intel Wireless Bluetooth components operating within Ring 0 (kernel mode). This flaw may allow a network adversary to cause a denial of service (DoS) without requiring authentication or user interaction. The attack complexity is low and can be performed via adjacent network access. The vulnerability impacts system availability but does not affect confidentiality or integrity. | GCVE Database | ||
| Medium | 6.8 | EPSS 0.1% | Medium6.8EPSS 0.1%GCVE Database CVE-2026-44625 is a use-after-free vulnerability in certain Intel Wireless Bluetooth components operating within Ring 0 (kernel mode). It may allow a local, authenticated, low-complexity attacker to cause a denial of service on the affected system. The vulnerability impacts system availability but does not affect confidentiality or integrity. No user interaction is required for exploitation, and special internal knowledge is not needed. No known exploits are reported in the wild, and no patch information is currently available. | GCVE Database | ||
| High | 7.4 | EPSS 0.2% | CVE-2026-115714Improper Certificate Validation High7.4EPSS 0.2%GCVE DatabaseCVE-2026-115714 An improper certificate validation vulnerability (CWE-295) exists in the operating system certificate bundle included in various Elastic products' Docker images and components. The bundle contains root CAs that trust eight eMudhra intermediate CAs whose private keys have been compromised. An attacker with network access between the product and a remote party could use these compromised keys to issue fraudulent certificates, enabling interception or modification of TLS-protected traffic. | GCVE Database | ||
| Medium | – | EPSS 0.2% | MediumEPSS 0.2%GCVE DatabaseCVE-2025-39797 This Red Hat security advisory addresses multiple vulnerabilities in the Linux kernel packages, which are critical components of the operating system. The update fixes several security issues including improper handling of duplicate SPI, improper class removal in network scheduling, Bluetooth device close handling, error path checks in nvmet-tcp, SCSI response data binding, host memory disclosure in nvme-tcp, and improper memory freeing in IPv4. Additionally, a local privilege escalation vulnerability related to skb_zerocopy ownership management is addressed. The advisory covers Red Hat Enterprise Linux 10.0 Extended Update Support and related builder products. A system reboot is required to apply these updates. | GCVE Database | ||
| High | 8.0 | EPSS 0.2% | CVE-2026-33245Red Hat Security Advisory: A Subscription Management tool for finding and reporting Red Hat product usage High8.0EPSS 0.2%GCVE DatabaseCVE-2026-33245 Red Hat Discovery is a subscription management tool that inspects and reports environment data, including system counts, operating systems, and configuration details. Several vulnerabilities, including CVE-2026-102276, affect components used by Red Hat Discovery. CVE-2026-102276 involves a denial of service caused by uncontrolled recursion in brace-expansion when processing crafted brace patterns, leading to application crashes. No fixes are currently available for these issues, and mitigations are limited or do not meet Red Hat's criteria. The vulnerabilities do not allow code execution or data compromise but can cause service interruptions. | GCVE Database | ||
| High | – | HighSecurityWeek Apple released updates for iOS and macOS 27.2 addressing 286 vulnerabilities, including memory corruption bugs, privilege escalation flaws, sandbox escapes, and remote code execution issues. A critical zero-day vulnerability in CoreGraphics, exploited in the wild, was backported and fixed in iOS 18.7.11. The updates also patch numerous security holes in components such as WebKit, kernel, image handling, and network services. Additional patches were released for other Apple operating systems and software. | SecurityWeek | |||
| High | 7.5 | EPSS 0.8% | High7.5EPSS 0.8%GCVE DatabaseCVE-2026-33814 Red Hat has released a security update for its MicroShift 4.18.57 build, addressing multiple vulnerabilities in the underlying Golang components. These include denial of service issues via malformed HTTP/2 frames, excessive recursion in ASN.1 unmarshalling, malicious MIME headers, quadratic complexity in URL path resolution, indefinite TLS KeyUpdate messages, and a cross-site scripting vulnerability in the HTML template package. The update is important for users operating MicroShift on edge devices to mitigate these risks. | GCVE Database | ||
| High | 8.7 | EPSS 0.7% | CVE-2026-105985craftcms cms · Template Injection High8.7EPSS 0.7%CVE Database V5CVE-2026-105985 Craft CMS versions 5.0.0 up to but not including 5.11.0 contain an authenticated remote code execution vulnerability in the Control Panel action app/render-components. Any authenticated user with basic Control Panel access can exploit this flaw by submitting specially crafted component classes and property overrides, leading to arbitrary Twig template code execution. This vulnerability allows execution of PHP functions such as system(), resulting in operating system command execution with the privileges of the web server process. The issue does not require admin privileges or access to sensitive settings or files. | CVE Database V5 | ||
| High | – | HighSANS ISC Handlers Diary Apple released its annual update across all its operating systems on September 14, 2026, patching 261 vulnerabilities, the highest number ever patched by Apple in a single update. The update includes new features and bug-fix-only releases for multiple OS branches including iOS, iPadOS, macOS, tvOS, watchOS, and visionOS. None of the patched vulnerabilities are reported as exploited in the wild. Some users have experienced issues with iOS 27 installation, and certain security-relevant applications require updates prior to upgrading to macOS 27. The vulnerabilities affect various components such as kernel, WebKit, Spotlight, and others, with impacts ranging from information disclosure to potential privilege escalation and denial-of-service. | SANS ISC Handlers Diary | |||
| –Not rated | – | Bleeping Computer Researchers have documented 39 distinct methods to compromise passkey-based authentication systems without breaking the underlying FIDO2 cryptography. These methods target the broader authentication ecosystem including user interfaces, synchronization services, enrollment, recovery processes, and trusted components such as browsers, operating systems, and cloud accounts. The attacks exploit architectural and procedural weaknesses rather than cryptographic flaws. Dedicated biometric hardware authenticators that do not rely on general-purpose devices or cloud synchronization significantly reduce the attack surface. Proper configuration of relying services to restrict enrollment and recovery to approved authenticators is critical to maintaining security. The existence of these attack methods highlights the importance of securing the entire authentication environment, not just the cryptographic protocol. | Bleeping Computer | |||
| Critical | 9.8 | EPSS 0.8% | CVE-2026-73749Aruba Networks ArubaOS-CX · Kwetsbaarheden Verholpen Critical9.8EPSS 0.8%GCVE DatabaseCVE-2026-73749 Multiple vulnerabilities have been addressed in Aruba Networks' ArubaOS-CX network operating system and its components, including the command line interface, API endpoints, and web-based management interface. The specific flaws involve various common weakness enumerations such as path traversal, command injection, format string vulnerabilities, cross-site request forgery, hardcoded cryptographic keys, buffer overflows, and others. No CVSS score or detailed impact metrics are provided, and no known exploits in the wild have been reported. No affected versions or patch information are explicitly stated. | GCVE Database | ||
| –Not rated | – | Kaspersky Security Blog Have you ever tried to open an “encrypted” email or an urgent document, only to realize with horror that your usual DOCX attachment is actually a file with the extension .docx.exe? Or maybe you received an email supposedly with an invoice, contract, or internal memo attached — only for the file to prove something entirely different from what it claimed to be? If so, you were likely targeted in a malware infection attempt. Cybercriminals routinely disguise malicious files as harmless documents and archives, banking on recipients blindly clicking without checking the extension. Kaspersky experts analyzed the file formats most frequently deployed in malicious email blasts to reveal what really lurks behind these extensions — and how attackers weaponize them in their campaigns. Important note: the extensions we’ll be discussing here are routinely used for completely legitimate files. For example, Windows executables normally end in .exe. However, we’re focusing specifically on scenarios where attackers disguise or spoof a file’s extension to pass it off as a totally different type of file. What extensions are most commonly found in malware? Our experts analyzed malicious email blasts from the beginning of 2026 to pinpoint the 15 most common dangerous file extensions. .exe .js .html .dll .bat .vbs .xls .pdf .jse .au3 .docx .htm .wsf .scr .lnk The top 15 file extensions used in malicious email blasts Let’s take a look at what files with these extensions actually do under the hood. Executable files An executable file is a compiled computer program that’s ready to run. Once launched, a malicious executable can download additional payloads, alter system settings, steal user data, connect your device to external attacker-controlled servers, and much more. These are the most common executable extensions found in malicious email campaigns: .exe .dll .com .scr .exe The classic Windows executable extension. It powers every program you use daily, from web browsers and games to office suites and software installers. By the way, attackers often wrap EXE malware in double extensions: invoice.docx.exe, report.pdf.exe, or even photo.jpg.exe. They take advantage of a default Windows setting: hiding extensions for known file types. Because this setting is turned on by default, users only see the first part of the file name — invoice.docx, report.pdf, or photo.jpg — and assume it’s just a normal document or image. But the second you open this trap file, the malware fires up. .dll Another common extension abused in malicious campaigns is .dll (dynamic-link library). These libraries hold functions that Windows programs frequently require while running, such as printing a document. This modular architecture prevents redundant code by letting multiple applications call on the exact same library for specific tasks. However, if an attacker replaces a legitimate library with an infected one, running any normal program that calls on it can trigger malicious code. .com While files with the .com extension have absolutely nothing to do with the web domain of the same name, cybercriminals likely count on victims mistaking these files for links in an unusual format. In reality, it’s a legacy Windows executable format. While modern versions of Windows no longer rely on this file type, the operating system can still run and execute it, which makes opening one a very bad idea. .scr SCR files are screensavers — those idle Windows screen animations featuring abstract patterns, the iconic bouncing logo, or whatever else. Despite their harmless reputation, screensavers are essentially executables just like EXE files: once opened, they can install extra components or alter system settings all the same. In malicious campaigns, these files routinely masquerade as images, screenshots, or documents. Scripts Scripts are text files containing a sequence of commands that a computer runs automatically in order. They can download files, install and launch programs, modify securi… | Kaspersky Security Blog | |||
| –Not rated | – | Krebs on Security The home appliance giant LG Electronics USA said this week it plans to suspend any apps built for its smart TVs that turn one’s television into an always-on residential proxy node. The move comes less than a month after researchers found that more than 42 percent of games and other apps available for download on LG’s webOS store allow unknown third-parties to route their Internet traffic through a user’s TV. Proxy SDK prevalence among smart TV apps for LG (webOS) and Samsung (Tizen OS) televisions. Image: Spur.us. On July 2, we featured research by the security firm Spur that examined the prevalence of residential proxy software development kits (SDKs) in smart TV apps. Spur found more than 42 percent of apps available for download on LG smart TVs include SDKs that turn one’s television in a proxy node indefinitely, and that more than a quarter of the apps made for Samsung’s Tizen operating system had similar residential proxy components. Responding to questions about Spur’s research, LG Senior Vice President John Taylor told KrebsOnSecurity the company was working with app developers to remove the residential proxy option from their apps on the webOS platform. Developers that fail to comply, he said, will find their apps suspended. “A residential proxy network is not an intended use for LG smart TVs, and LG Electronics is working with developers to remove the residential proxy option from their apps on the webOS platform,” Taylor said. “If this option is not removed, these apps will be suspended.” Taylor said LG is committed to keeping residential proxy networks out of its smart TV apps going forward, and that the company’s review of those apps is “well underway now.” “As part of our ongoing efforts to enhance platform quality and the user experience, LG will continue to strengthen our evaluation process for developer-submitted apps, including those that incorporate residential proxy SDKs,” Taylor wrote in an emailed statement. App makers looking for ways to monetize their creations can turn to residential proxy providers, which pay developers to include SDKs that turn the user’s device into a residential proxy node that is rented to paying customers. In the case of LG and Samsung smart TVs, Spur found residential proxy SDKs bundled with everything from simple games like Pac-Man to screensavers and file utilities. A Pac-Man smart TV app from Bright Data offers users the choice between viewing ads in the game or agreeing to allow their TV to serve as a residential proxy node. Image: Spur.us. Spur’s report found the residential proxy network Bright Data accounted for a majority of proxy SDKs across both Samsung and LG smart TVs. In a statement shared with KrebsOnSecurity, Bright Data said its network is built on consent and responsibility and operates by LG and Samsung terms. “Every peer opts in through a dedicated screen and receives value in return; every customer is vetted, and our practices have now undergone a second independent audit by PwC,” the statement reads. “We remain committed to an open, transparent internet where legitimate businesses, researchers, and institutions can responsibly access data that lives in the public domain.” Bright Data and other proxy providers named in Spur’s report all say they follow rigorous know-your-customer processes to validate legitimate uses of their services, which is often heavily tied to content-scraping activities by said customers. The proxy companies also say they incorporate technological countermeasures to prevent proxy service customers from being able to interact with and control other devices on the proxy user’s local network . Spur argues the problem is not that residential proxy networks exist, but rather that they are being embedded at scale in devices that most consumers do not think of as computers and are not equipped to audit. “A one-time consent prompt buried in a TV app is not a substitute for meaningful transparency, ongoing control, and platform oversight,” Spur’… | Krebs on Security | |||
| –Not rated | – | Check Point Research Note: SysAid was not compromised, and no SysAid vulnerability was involved. The attacker had already gained access to the victim environment and abused a legitimate software-deployment feature to deploy malware onto another machine within it. Key Points Check Point Research (CPR) tracks ‘ Cavern Manticore ’ as an Iran-nexus threat actor operating against Israeli targets , with a focus on the government and IT sectors. Cavern Manticore shares technical overlaps with other Iranian MOIS (Ministry of Intelligence and Security)-linked threat actors, including MuddyWater and Lyceum . CPR observed a modular C2 framework in the wild, with all samples built on top of .NET but compiled into different output formats. These components are used as Cavern agent and Cavern modules . The framework’s anti-analysis posture relies on uncommon .NET compilation formats ( Mixed-Mode C++/CLI and Native AOT ) that force reverse engineers into multiple toolsets and metadata-reconstruction workflows, together with per-module AppDomain isolation as an anti-forensics measure. In malware-engine coverage, the majority of observed samples score zero or very low detection rates on VirusTotal. Post-exploitation modules provide the threat actor with extended capabilities , including file system and database browsing, LDAP querying, network reconnaissance, and tunneling. In multiple observed intrusions, the initial foothold was achieved through abuse of existing Remote Monitoring and Management ( RMM ) software deployed in the targeted organization. Introduction Since early 2026, Check Point Research (CPR) has tracked a new modular command-and-control framework used by Cavern Manticore , an Iran-nexus APT group primarily targeting Israeli organizations, with a focus on IT providers, and government sectors. Cavern Manticore is an Iran MOIS (Ministry of Intelligence and Security)-linked actor, with links to the OilRig subgroup named Lyceum . The framework reflects a mature and adaptable toolset built around a shared .NET foundation, while using multiple compilation formats across different components, including .NET Framework , .NET Mixed-Mode C++/CLI , and .NET Native AOT . The compilation format itself becomes the anti-analysis layer that forces reverse engineers into multiple toolsets and metadata-reconstruction workflows. During our investigation, we observed both Cavern agents and Cavern modules in the wild, highlighting a modular architecture that separates core communication capabilities from mission-specific post-exploitation functionality. This design allows the operators to tailor deployments per victim environment, limit what defenders and analysts can recover from any single victim and extend access after compromise through specialized modules for reconnaissance, data access, tunneling, and lateral movement. Figure 1: Cavern Modules Evade Malware Engines. Technical Analysis: Cavern – A Modular .NET C2 Framework 1. Cavern at a Glance Cavern is a modular post-exploitation C2 framework built entirely on .NET, but deliberately compiled into three different binary formats: .NET Framework ( IL-only ), Mixed-Mode C++/CLI ( IL + Native ), and .NET 8 NativeAOT ( Native-only ). The recovered execution chain begins with SysAid’s software update feature, which the actor leverages to deploy a WinDirStat DLL sideloading package to C:\ProgramData\WinDir\WinDirStat.exe . The legitimate WinDirStat.exe binary loads the trojanized uxtheme.dll , which is the Cavern Agent , and the agent in turn loads a dedicated native communication module n-HTCommp.dll to reach the C2 and then pulls down additional post-exploitation modules on operator command. Figure 2: Cavern Agent Execution Chain. The table below provides an overview of the modules. Component Internal Name Format Role Cavern Agent uxtheme.dll Mixed-Mode C++/CLI (.NET 4.7.2, IL + Native) Core backdoor, module orchestrator Communication Module n-HTCommp.dll NativeAOT (.NET 8, Native-only) HTTPS/WebSocket transport, XOR… | Check Point Research | |||
| Medium | 5.3 | EPSS 0.5% | Medium5.3EPSS 0.5%GCVE Database ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, an unauthenticated P2P peer can cause the mempool download pipeline to retain transactions after verification reaches the outer RATE_LIMIT_DELAY timeout. In zebrad/src/components/mempool/downloads.rs, Downloads::poll_next removed cancel_handles entries after success and ordinary verification errors, but tokio::time::error::Elapsed did not carry the UnminedTxId needed to remove the timed-out entry. Each retained cancel_handles entry could hold a full Gossip::Tx(UnminedTx), while normal mined-transaction cleanup could not match attacker transactions and no periodic garbage collection or count cap existed. Sustained traffic therefore caused monotonic memory growth until swap pressure degraded the node or the operating system terminated the zebrad process for exhausting memory. This issue is fixed in version 4.5.0. | GCVE Database | ||
| High | 7.4 | EPSS 0.6% | CVE-2026-48787flipped-aurora gin-vue-admin · OS Command Injection High7.4EPSS 0.6%CVE Database V5CVE-2026-48787 gin-vue-admin is an AI-assisted basic development platform. In version 2.9.1, an authenticated attacker with access to the code-generation feature and MCP management interface can exploit this vulnerability by injecting attacker-controlled Go source code through POST /autoCode/addFunc, and then invoking POST /autoCode/mcpStart to trigger a rebuild and restart of the standalone MCP service. This allows arbitrary operating system commands to be executed on the server with the privileges of the application process. Successful exploitation may lead to remote code execution (RCE), modification of backend source code or runtime logic, deployment of persistent backdoors, access to or manipulation of application data and configuration, and further impact on local resources running under the same service account or privilege context. The risk is highest in deployments that retain the source tree, allow writes to source files, and support local build or startup of standalone MCP components. In environments using binary-only releases, read-only filesystems, or with local build capabilities removed, the exploitability of the full attack chain is significantly reduced. However, once the online code-generation capability and MCP-hosted startup workflow are enabled, the overall security impact may reach high to critical severity. As of time of publication, it is unknown if a patched version is available. As a workaround, enforce strict allowlist validation on path- and identifier-related fields such as `humpPackageName`, `packageName`, `FuncName`, and `Router`, and only permit safe identifier formats. | CVE Database V5 |
Page 1 of 2 · 1 duplicate CVE record merged