Search: network-lab.info
911 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Medium | 7.8 | EPSS 0.1% | Medium7.8EPSS 0.1%GCVE DatabaseCVE-2026-53089 A use-after-free vulnerability in the Linux kernel's BPF subsystem was fixed. The issue occurs when querying information for offloaded BPF maps or programs, where a network namespace reference count may reach zero during destruction, causing a use-after-free condition. The fix replaces get_net() with maybe_get_net() to safely handle network namespace reference counts. This vulnerability affects multiple Linux kernel versions prior to 7.0.0-28.28 and related builds. A patch is available and should be applied to mitigate the issue. | GCVE Database | ||
| Malicious | – | MaliciousGCVE Database The npm package signup-embedder versions 99.99.99-poc2, 99.99.99-poc3, and 99.99.99 contain malicious preinstall and postinstall scripts that automatically execute during installation. These scripts collect detailed host environment information and send it to an attacker-controlled server, enabling internal network mapping and potential follow-on attacks. The package is publicly available on the npm registry and masquerades as a proof-of-concept for dependency confusion. Systems that install this package risk full compromise, and secrets stored on affected machines should be rotated immediately. | GCVE Database | |||
| Medium | 4.4 | EPSS 0.2% | CVE-2026-54325earendil-works pi · Untrusted Functionality Inclusion Medium4.4EPSS 0.2%CVE Database V5CVE-2026-54325 # Pi loads project-local extensions without approval Pi before 0.79.0 loaded project-local configuration and resources from a repository's `.pi` directory without first asking the user to trust that repository. This included project-local extensions, which are executable TypeScript or JavaScript modules loaded into the Pi process. An attacker who controls a repository could place Pi-specific project resources in that repository. If a user then started Pi from that working tree, the project-local extension code could run with the same privileges as the local Pi process without the user having a convenient way to make a trust decision. ## Info The affected component is Pi's project resource loading path. Before 0.79.0, startup loaded project `.pi/settings.json`, auto-discovered `.pi` resources, project package-managed resources, and project instruction files as part of normal session initialization. Project-local extensions were included in the same extension set as user/global extensions and were initialized before there was a project trust boundary. Extensions like pi itself are not sandboxed. They run in the Pi process and can register commands, tools, and event handlers. The vulnerable behavior was not a privilege escalation across an operating-system boundary, but it allowed repository-controlled Pi extension code to execute implicitly when a user ran Pi in that repository. ## Impact Exploitation requires user interaction: the attacker must get a user to open or otherwise work in an attacker-controlled repository and start Pi there. The attacker does not need an account on the user's machine or prior privileges in Pi. If exploited, project-local extension code runs with the same permissions as the user running Pi. It can access files, environment variables, credentials available to the process, the network, and local tools available to that user. In CVSS terms, this advisory rates the impact as limited confidentiality and integrity impact without a distinct availability impact because exploitation requires local user action in an untrusted repository and does not cross a privilege boundary. This risk is most relevant for users who run Pi in repositories they have not reviewed or do not trust. Pi's security guidance requires users to trust the codebases they work with, or to use an external sandbox or isolation boundary for untrusted repositories. ## Affected versions - Affected: `< 0.79.0` - Patched: `0.79.0` ## The solution Pi 0.79.0 added project trust gating for project-local inputs. On interactive startup, Pi now asks before loading project-local settings, instructions, resources, package-managed resources, or extensions when a trust decision has not already been saved for the working directory. Non-interactive modes do not prompt. Without a saved trust decision, they ignore project-local inputs unless `--approve` or `-a` is passed. Users can also pass `--no-approve` or `-na` to ignore project-local inputs for a single run even when a project is already trusted. Before trust is resolved, Pi loads only user/global extensions and extensions passed explicitly on the command line. Those extensions can participate in the `project_trust` event; project-local extensions are not loaded until after the project is trusted. ## Recommendations Upgrade `@earendil-works/pi-coding-agent` to version 0.79.0 or later. After upgrading, review project trust prompts carefully and only trust repositories whose Pi-specific configuration and extensions you are willing to run. The upgrade makes this trust decision explicit, but it does not change Pi's security model: users should work only in trusted repositories, or use external isolation for untrusted code. Use `--no-approve` for one-off runs where project-local inputs should be ignored. For untrusted repositories or unattended automation, follow Pi's [security guidance](https://pi.dev/docs/latest/security) and run Pi inside an operating-system sandbox, container, VM, or other isolation boundary with only the files and credentials required for the task. ## Workarounds Before and after this change, Pi users should only run Pi in repositories they trust, or in an external sandbox or isolation boundary when working with untrusted code. Pi 0.79.0 adds an explicit trust prompt as a defense-in-depth and user-safety improvement; it is not a sandbox and it does not make untrusted repositories safe. If upgrading is not possible and your workflow already enforces this trust boundary, continue to avoid running Pi directly in untrusted repositories. Inspect and remove project-local Pi configuration and resources before use, especially project-local extensions and package configuration. Disabling extensions and other project resources with command-line flags can reduce exposure, but trusted or isolated execution remains the primary mitigation. ## Timeline - 2026-05-25: Report received. - 2026-06-05: Project trust gating committed. - 2026-06-08: Project trust refi | CVE Database V5 | ||
| –Not rated | – | SecurityWeek Dragos has launched EmberAI, an AI-powered capability designed specifically for operational technology (OT) cybersecurity. EmberAI leverages Dragos' extensive OT cybersecurity dataset compiled over a decade, enabling analysts to query threat and risk information in plain language. The AI correlates multiple data sources, including threat intelligence, assets, vulnerabilities, and network activity, providing context-aware responses to help prioritize and tailor incident response. EmberAI operates within the customer's environment, ensuring data privacy, and maintains transparency and auditability of its recommendations. This product is generally available as part of the Dragos platform. | SecurityWeek | |||
| High | 7.1 | EPSS 0.6% | High7.1EPSS 0.6%CVE Database V5CVE-2026-56210 A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows setting a spatial_layer_id exceeding the configured number of layers. This causes an out-of-bounds heap read of approximately 40,728 bytes when computing a layer context array index. An attacker who can influence SVC encoder parameters in a network-facing service could exploit this for information disclosure (heap content leak) or denial of service (segmentation fault from hitting unmapped memory). | CVE Database V5 | ||
| High | 7.1 | EPSS 0.6% | High7.1EPSS 0.6%CVE Database V5CVE-2026-56209 An arbitrary address write vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows an attacker to inject an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. The encoder then writes approximately 1,200 bytes at the attacker-controlled address. This is fully deterministic and does not require a separate information leak. An attacker who can supply frames to a network-facing libaom encoder with SVC enabled could exploit this for denial of service or potential code execution. | CVE Database V5 | ||
| –Not rated | – | Reddit BlueTeam Brovan is a user-mode x86_64 binary emulator designed for reverse engineering and malware analysis. It supports emulation of Windows PE binaries, Linux ELF binaries, memory dumps, and even raw or unrecognized binaries. The tool allows interactive inspection of execution, syscall and function tracing, and controlled sandboxed execution without running code directly on the host CPU. It also captures emulated network traffic for analysis. Brovan aims to facilitate flexible binary research by providing full control over execution and runtime behavior in a contained environment. It is currently in early stages but actively developed and available as open source. | Reddit BlueTeam | |||
| High | 8.1 | EPSS 0.4% | CVE-2026-46927Oracle Receivables · Missing Authentication High8.1EPSS 0.4%CVE Database V5CVE-2026-46927 CVE-2026-46927 is a high-severity vulnerability in Oracle Receivables, part of Oracle E-Business Suite versions 12.2.3 through 12.2.15. It allows an unauthenticated attacker with network access via SOAP to potentially take over the Oracle Receivables component. The vulnerability has a CVSS 3.1 base score of 8.1, indicating high impact on confidentiality, integrity, and availability. Oracle has published a Critical Security Patch Update advisory recommending prompt patching to address this and other vulnerabilities. No explicit patch version or fix details are provided in the advisory content, so users should consult the official Oracle advisory for the latest remediation information. | CVE Database V5 | ||
| Critical | 9.1 | EPSS 0.4% | Critical9.1EPSS 0.4%CVE Database V5CVE-2026-46784 CVE-2026-46784 is a critical vulnerability in Oracle WebCenter Content: Imaging versions 12.2.1.4.0 and 14.1.2.0.0. It allows an unauthenticated attacker with network access via HTTP to gain unauthorized creation, deletion, or modification access to critical data or all accessible data within the product. The vulnerability has a CVSS 3.1 base score of 9.1, indicating high confidentiality and integrity impact without requiring user interaction or privileges. Oracle has acknowledged this vulnerability in its June 2026 Critical Security Patch Update advisory and strongly recommends applying the provided patches promptly to mitigate the risk. No specific patch links were provided in the input, but the vendor advisory contains patch availability information. Until patches are applied, risk reduction may be possible by blocking required network protocols or restricting privileges, though these may impact functionality. | CVE Database V5 | ||
| Medium | 4.8 | EPSS 0.3% | CVE-2026-10634zephyrproject zephyr · Use After Free Medium4.8EPSS 0.3%CVE Database V5CVE-2026-10634 Zephyr's native TCP stack iterates the global connection list in net_tcp_foreach() (subsys/net/ip/tcp.c) using the SYS_SLIST_FOR_EACH_CONTAINER_SAFE macro, which caches a pointer to the next list node. Prior to this fix the function released tcp_lock while invoking the per-connection callback and re-acquired it afterwards. During that window a concurrent tcp_conn_release(), running on the dedicated TCP work-queue thread when a connection's reference count drops to zero (e.g. a remote peer closing or resetting the connection), can remove and k_mem_slab_free() the cached next connection. When the iterator advances it dereferences the freed (and possibly reallocated) slab memory — a use-after-free that can crash the system (denial of service) and, if the slot has been reused, cause the callback to operate on an attacker-influenced object (potential information disclosure or further fault). net_tcp_foreach() is reached in production via the net conn network shell command and via net_tcp_close_all_for_iface() on interface-down; the freeing side is driven by ordinary TCP traffic. The fix moves the connection/context teardown in tcp_conn_release() inside the tcp_lock critical section and keeps tcp_lock held across the callback in net_tcp_foreach(). The defect was introduced with the modern (TCP2) stack in 2020 and affects releases up to and including v4.4.0. | CVE Database V5 | ||
| Medium | 5.1 | EPSS 0.2% | CVE-2026-50099Naxclow Smart Doorbell X3 · Insertion of sensitive information into Externally-Accessible file or directory Medium5.1EPSS 0.2%CVE Database V5CVE-2026-50099 During WiFi association, Naxclow device firmware prints the host network’s SSID, PSK, and negotiated WPA keys in cleartext to an exposed UART console on production hardware. The UART pads are labeled, run with default serial settings, and drop to an interactive RT-Thread shell that permits arbitrary memory reads, enabling full firmware extraction. An attacker with brief physical access, common for outdoor-mounted devices, can therefore recover WiFi credentials and bootstrap firmware-side attacks. | CVE Database V5 | ||
| Critical | 9.8 | EPSS 0.4% | CVE-2026-11561Soagen Informatics Technologies Software and Consulting Apinizer · Expression Language Injection Critical9.8EPSS 0.4%CVE Database V5CVE-2026-11561 CVE-2026-11561 is a critical vulnerability in Soagen Informatics Technologies Software and Consulting Inc.'s Apinizer product. It involves improper neutralization of special elements used in an expression language statement, leading to expression language injection and potential code injection. The affected versions include Apinizer 2026.04.0 through versions before 2026.04.6. The vulnerability has a CVSS score of 9.8, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and full confidentiality, integrity, and availability impact. No official patch or remediation guidance is currently available from the vendor. No known exploits in the wild have been reported. | CVE Database V5 | ||
| Unrated | – | EPSS 0.5% | UnratedEPSS 0.5%GCVE DatabaseCVE-2026-9716 Multiple vulnerabilities have been identified in Schneider Electric's PowerLogic™ P7 product, affecting versions up to 0.2.003.001. The vendor recommends strict adherence to industry cybersecurity best practices to mitigate risks, including network isolation, physical security controls, controlled access to programming modes, and secure remote access methods. No specific details about the vulnerabilities or exploits are provided, and no patch information is available. | GCVE Database | ||
| Medium | – | MediumTenable Research On June 2, 2026, the White House signed an Executive Order directing federal agencies to harden their systems with AI-enabled cyber defenses and to stand up a new AI cybersecurity clearinghouse — most of it on a 30-day clock. Here’s what the EO requires and how Tenable can help. Key takeaways: The new AI Security Executive Order will require national security and civilian federal agencies to prioritize cyber defenses to account for new frontier AI model capabilities. Tenable is well positioned to help federal agencies gain visibility across their environments, including AI assets, and to prioritize the vulnerabilities and other exposures that pose the highest risk; Tenable AI-enabled exposure management capabilities can help support vulnerability remediation and automate multi-step remediation workflows. The vulnerability and patching clearinghouse which will be developed under the Executive Order will require strong engagement from private sector partners, including Tenable, to drive actionable insights on AI-associated vulnerabilities and mitigation prioritization. On June 2, 2026, the President signed an Executive Order (EO) titled “ Promoting Advanced Artificial Intelligence Innovation and Security .” The direction is clear and the calls to action are fast-moving. Within 30 days: Federal agencies must begin hardening their information systems with AI-enabled cyber defenses. CISA must issue new directives or guidance for civilian agencies. The Department of the Treasury (Treasury), with the National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA), must stand up a new AI cybersecurity clearinghouse focused on finding and fixing software vulnerabilities. Within 60 days, Treasury, with the Department of War (DoW), NSA and CISA, in consultation with the White House and other agencies, must establish a classified benchmarking process to assess the capabilities of frontier AI models through voluntary collaboration with AI developers. While the Executive Order applies to U.S. federal agencies, the need to prepare for changes in the threat landscape brought about by the advanced cyber capabilities of frontier AI models applies to any organization that needs to manage cyber risk. Here’s a breakdown of what the AI EO requires, the deadlines that matter, and where Tenable fits. What the AI Executive Order requires The EO’s operative provisions sit in Section 2 (“Upgrading American systems for advanced AI”) and Section 3 (“Secure frontier model deployment”). The cybersecurity core is in Section 2. Within 30 days: National security and defense systems. The Committee on National Security Systems must prioritize the cyber defense of National Security Systems (NSS) and the Secretary of War must do the same for DoW information systems (Section 2(a) and 2(b)). Civilian federal systems and critical infrastructure. CISA, in consultation with the Office of Management and Budget (OMB), the Assistant to the President for National Security Affairs, and the National Cyber Director, must release Binding Operational Directives (BODs) “and other guidance as appropriate” to: Expedite and prioritize the cyber defense of civilian federal information systems. Establish or expand federal programs and services that enhance AI-enabled defensive tools. Facilitate access to cybersecurity tools and services, including where appropriate, covered frontier models, for agencies, state and local authorities, and critical infrastructure operators such as rural hospitals, community banks, and local utilities. Worth noting, while the EO directs CISA to release BODs or other guidance for federal civilian agencies, the specific implementation directives are not yet known (Section 2(c)). The AI cybersecurity clearinghouse. The Secretary of the Treasury, with the National Cyber Director, NSA, and CISA, must form an AI cybersecurity clearinghouse, in voluntary collaboration with the AI industry and critical infrastructure operators. The EO tasks the clearinghouse with three concrete functions, per Section 2(d): Coordinate and deconflict scanning for software vulnerabilities Discover and validate those vulnerabilities Coordinate and prioritize the remediation and distribution of vulnerability patches. Grant funding for AI vulnerability detection. OMB, with the National Cyber Director and CISA, must determine whether existing federal grant programs have funding that can be directed toward applicants developing advanced AI vulnerability detection (Section 2(e)). Within 60 days: Cybersecurity workforce. The Office of Personnel Management must expand hiring and placement pathways for cybersecurity specialists through the United States Tech Force (Section 2(f)). Secure frontier model deployment. Treasury, NSA, and CISA, in consultation with NIST and others, must develop a classified benchmarking process to assess the advanced cyber capabilities of AI models. They must also set the threshold for designating a “covered frontier model,” and design a voluntary framework through which developers can give the government up to 30 days of pre-release access to those models. The Executive Order is explicit that it does not create any mandatory licensing, preclearance, or permitting requirement for AI models (Section 3). No fixed deadline: Criminal enforcement. The EO directs the Attorney General to prioritize enforcement against those who use AI to illegally access or damage computer systems (Section 4). For federal cybersecurity leaders, this is less a future-state policy document than a near-term planning trigger. Watch for CISA’s issuance of BODs and other guidance, and for readouts on the clearinghouse, during June and July. How Tenable can help The EO’s center of gravity — finding software vulnerabilities, validating them, prioritizing them, and driving remediation — is the work Tenable's platform is built to do. While the AI Executive Order focuses on vulnerability discovery, validation, prioritization, and remediation, the benefit of the Tenable One Exposure Management Platform is that it addresses vulnerabilities alongside other security weaknesses, including misconfigurations of AI systems and overpermissioned AI agents, to serve as the system of action for mitigating cyber exposure and reducing cyber risk across organizations’ expanding attack surfaces. Below, learn how specific Tenable capabilities map to the EO’s requirements. Continuous vulnerability detection across the attack surface Sections 2(a) through 2(d) turn on the ability to find vulnerabilities across a wide range of systems continuously. Tenable One Vulnerability Management and Tenable Security Center provide network-based and agent-based assessment across IT assets, with credentialed scanning for greater depth. Tenable One Cloud Exposure extends that visibility to cloud workloads and configurations, and Tenable One Attack Surface Management maps internet-facing assets that agencies may not know they have. For agencies operating classified or air-gapped environments — relevant to the National Security Systems named in Section 2(a) — Tenable Enclave Security is built to run vulnerability and configuration assessment inside those boundaries. Risk-based prioritization, not “patch everything” Section 2(d) doesn’t only call for discovering vulnerabilities — it calls for prioritizing them for remediation. That distinction matters because no agency can patch everything at once. Tenable’s Vulnerability Priority Rating (VPR) uses machine learning, trained on the company’s corpus of more than 1.7 trillion security findings accumulated over more than 25 years of continuous scanning, to forecast which vulnerabilities are most likely to be exploited, so defenders can focus on the smaller set that represents real, immediate risk. By leveraging AI-generated features and expert intelligence from Tenable's Research Special Operations team, VPR helps organizations pinpoint the critical 1.6% of vulnerabilities that represent actual business risk . Tenable also ingests CISA’s Known Exploited Vulnerabilities (KEV) catalog — the continuously updated, authoritative list of Common Vulnerabilities and Exposures (CVEs) under active exploitation — directly into prioritization, aligning remediation guidance to the same source CISA uses to track risk across the federal enterprise. AI-enabled defensive tooling Section 2(c) directs CISA to establish or expand programs that enhance AI-enabled defensive tools. As frontier AI models accelerate the rate at which vulnerabilities can be discovered and exploited , the traditional window for manual remediation is rapidly closing. The June 2026 AI Executive Order recognizes this shift, directing federal agencies to counter machine-speed threats with AI-enabled cyber defenses within 30 days. Tenable Hexa AI , the agentic engine of the Tenable One Exposure Management Platform , is designed to help counter machine-speed threats, supercharge productivity, and accelerate risk reduction by automating multi-step remediation workflows. Security teams can leverage pre-built agents directly in the user interface or build custom agents via the Model Context Protocol (MCP), turning exposure intelligence into decisive action at machine speed. At the same time, as agencies build custom models or adopt third-party tools like ChatGPT and Copilot, they fundamentally expand their attack surface. It is now critical to protect enterprise AI, shadow AI, training data, and underlying infrastructure from emerging threats like adversarial attacks, data poisoning, and model theft. Tenable secures this expanding attack surface with Tenable One AI Exposure , which is designed to help agencies see, manage, and control the risks introduced by generative AI. Tenable One AI Exposure allows agencies to discover and inventory AI tools and libraries, and apply AI usage policies across the environment — a growing requirement as agencies adopt AI and need to account for it as part of | Tenable Research | |||
| Medium | 6.8 | EPSS 0.2% | CVE-2026-48040netty-incubator-codec-ohttp · Out-of-bounds Read Medium6.8EPSS 0.2%CVE Database V5CVE-2026-48040 The netty incubator codec.bhttp is a java language binary http parser. The library implements Oblivious HTTP (RFC 9458) using BoringSSL's HPKE C library via JNI. When deriving native memory addresses for cryptographic operations versions prior to 0.0.22.Final provide a fallback path for direct ByteBufs that do not expose their memory address through `hasMemoryAddress()`. This fallback occurs when `sun.misc.Unsafe` is unavailable to Netty — for example, when the JVM is started with `-Dio.netty.noUnsafe=true`, when a SecurityManager restricts Unsafe access, or when running on non-HotSpot JVMs. In these configurations, Netty's default `PooledByteBufAllocator` returns `PooledDirectByteBuf` instances for which `hasMemoryAddress()` returns false. Under the enabling JVM configuration, an unauthenticated network attacker can cause the OHTTP gateway to corrupt memory belonging to other concurrent connections and disclose the contents of adjacent pooled direct buffers by triggering cryptographic operations with crafted OHTTP requests. The corruption occurs regardless of whether the AEAD tag verification succeeds, as BoringSSL zeroizes the output buffer on failure. The information disclosure path provides the attacker with the encryption key needed to extract the leaked data. This violates the confidentiality and integrity of all connections sharing the same Netty buffer arena. Version 0.0.22.Final fixes the issue. | CVE Database V5 | ||
| –Not rated | – | Reddit Malware A Reddit post in the r/Malware subreddit highlights suspicious behavior related to the MEmu Android emulator. The post notes that a Microsoft Edge browser policy allowing local network access is installed and linked to a domain owned by MEmu's parent company, Shanghai Maiwei Software Technology Co. , Ltd. The concern is why this policy is present, as it permits sites to make network requests to local devices and endpoints. No direct evidence of exploitation or malware is provided, and no official vendor advisory or patch information is available. | Reddit Malware | |||
| –Not rated | – | Reddit BlueTeam The PCPJack threat actor compromised approximately 230 cloud servers and repurposed them into a hidden SMTP relay network. The attacker left their deployment toolkit publicly accessible in an unauthenticated open directory, facilitating discovery and analysis. Indicators include a systemd service named xsync disguised as a system sync utility, files under /var/tmp/. xs, and Chisel reverse SOCKS5 tunnels on ports 10000-14999. A public blog post provides detailed MITRE ATT&CK mappings and HuntSQL detection queries. No official patch or remediation guidance is currently available. | Reddit BlueTeam | |||
| Medium | 4.3 | EPSS 0.2% | CVE-2026-36615Mercusys AC12G · Information Exposure Medium4.3EPSS 0.2%CVE Database V5CVE-2026-36615 Mercusys AC12G (EU) V1 with firmware AC12G(EU)_V1_200909 has an undocumented /agileconfigreset endpoint that allows unauthenticated attackers on the adjacent network to access internal buffer contents. This vulnerability exposes sensitive information without requiring authentication. The CVSS score is 4.3, indicating a medium severity level. No patch or official remediation guidance is currently available. | CVE Database V5 | ||
| Medium | – | CVE-2026-49389Netatalk · [Unknown description] MediumGCVE DatabaseCVE-2026-49389 CVE-2026-49389 is a medium severity vulnerability affecting multiple specific versions of Netatalk, a network file sharing software. The exact nature and technical details of the vulnerability are unknown based on the provided information. There is no CVSS score or detailed description available. No known exploits are reported in the wild. The affected versions are explicitly listed and pertain to various Ubuntu package releases of Netatalk. No patch or remediation information is provided. | GCVE Database | |||
| Medium | 6.5 | EPSS 0.2% | CVE-2026-49385JetBrains YouTrack · Missing Authorization Medium6.5EPSS 0.2%CVE Database V5CVE-2026-49385 CVE-2026-49385 is a medium severity vulnerability in JetBrains YouTrack before version 2026.1.13570. It involves improper access control (CWE-862) that allows low-privileged users to modify service accounts. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a network attack vector with low complexity and no user interaction required. There is no confirmed patch or official remediation information available at this time. No known exploits are reported in the wild. | CVE Database V5 |
Page 30 of 49