ContextForge is an AI gateway, registry, and proxy that provides centralized discovery, guardrails, and management for MCP, A2A, and REST or gRPC APIs. Prior to 1.0.3, the /admin/gateways/test call site in mcpgateway/admin.py calls validate_gateway_test_url() in mcpgateway/common/validators.py to resolve and reject private, loopback, link-local, and cloud-metadata addresses, but ResilientHttpClient later resolves the original hostname again without binding the validated address. When MCPGATEWAY_ADMIN_API_ENABLED is enabled, an attacker with a database-backed role containing explicit gateways.read permission can use DNS rebinding to return a public address during validation and a private or metadata address during connection, bypassing ssrf_blocked_networks and ssrf_dns_fail_closed because those controls apply only to the validation-time result. The endpoint's allow_admin_bypass=False setting means a bootstrap-only virtual platform-admin identity without a database role is not sufficient. Successful exploitation can reach internal services and cloud metadata, expose cloud credentials, access internal APIs, or probe internal network ports. This issue is fixed in version 1.0.3.
A security flaw has been discovered in Open5GS up to 2.7.x. Affected is the function amf_nnrf_try_old_amf_discovery_fallback of the file src/amf/nnrf-handler.c of the component Old AMF Discovery Fallback. The manipulation of the argument discovery_option results in use after free. The attack may be performed from remote. The patch is identified as ddd683a35f8aaac2b7b9884a24cd53bddfc65238. Applying a patch is advised to resolve this issue.
libp2p-rendezvous through 0.17.1 fails to validate registration TTL values in discovery responses, allowing attackers to trigger timer arithmetic overflow. A malicious rendezvous server can send a discovery response with an unbounded TTL value that causes the client node process to panic when computing the expiry timer.
An unauthenticated network-adjacent attacker can leverage discovery to capture cluster administrative credentials during the initial cluster connection handshake.
This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0.
Users are recommended to upgrade to version 2.57.0, which fixes the issue.
eprosima Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group). Versions prior to 2.6.12, 2.14.6, 3.2.4, 3.3.1, and 3.4.2 have a remotely triggerable Out-of-Bounds Read while processing RTPS `DATA_FRAG` submessages. An attacker can craft a `DATA_FRAG` with a large `sampleSize` but a small actual payload, and set `fragmentsInSubmessage` such that the receiver treats the packet as the LAST fragment**. In this LAST-fragment path, Fast-DDS computes `incoming_length` based on `sampleSize` and calls `memcpy()` without validating `incoming_data.length >= incoming_length`. As a result, `CacheChange_t::add_fragments()` reads past the received UDP datagram buffer and into adjacent heap memory, copying those bytes into the reassembly buffer. In a Discovery Server deployment, the resulting `CacheChange_t` can be relayed to other participants, meaning that a newly joining participant may receive leaked heap memory (e.g., pointer values that could aid ASLR bypass). Versions 2.6.12, 2.14.6, 3.2.4, 3.3.1, and 3.4.2 fix the issue.
In the Linux kernel, the following vulnerability has been resolved: x86/mce: Set up the polling timer before CMCI discovery I hit the following on one of my machines: mce: CPU0 BANK15 CMCI inherited storm ------------[ cut here ]------------ ODEBUG: assert_init not available (active state 0) object: (____ptrval____) object type: timer_list hint: 0x0 WARNING: lib/debugobjects.c:632 at debug_object_assert_init+0x178/0x230, CPU#0: swapper/0/0 CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc5 #3 PREEMPTLAZY RIP: 0010:debug_object_assert_init+0x18f/0x230 Call Trace: <TASK> __mod_timer mce_timer_kick cmci_discover intel_init_cmci mce_intel_feature_init mcheck_cpu_init identify_cpu identify_boot_cpu arch_cpu_finalize_init start_kernel A second splat follows right after, from timer_setup() finding that same timer already queued: ODEBUG: init active (active state 0) object: (____ptrval____) object type: timer_list hint: stub_timer+0x0/0x10 This is happening because CMCI storm detection is trying to modify the timer before latter was properly set up. Set up the timer first. __mcheck_cpu_setup_timer() only calls timer_setup(), and depends on neither the generic nor the vendor init. [ bp: Massage commit message. ]
HiddenLayer, an Austin-based AI security company, announced raising $100 million in Series B funding to enhance its platform for securing AI coding agents and agentic AI applications. The company focuses on runtime security capabilities to detect and prevent anomalous, unauthorized, or malicious behavior by AI agents in production environments. HiddenLayer's platform offers discovery, AI supply chain security, attack simulation, and runtime protection to ensure compliance and intellectual property protection for enterprises adopting AI. The funding will support expanding these capabilities to secure autonomous AI agents that write, review, and ship code with minimal human oversight.
LibreNMS versions 23.10.0 up to but not including 26.2.0 contain an authenticated OS command injection vulnerability in the libvirt discovery feature. This occurs when libvirt support is enabled, allowing an authenticated admin to inject arbitrary OS commands via a crafted device hostname. The vulnerability is fixed in version 26.4.0.
This entry references a GitHub account hosting a collection of Python networking and cybersecurity projects. The content is a link post from a Reddit cybersecurity subreddit where the user shares their GitHub repository containing tools for host discovery, port scanning, TCP communication, banner grabbing, and service enumeration. There is no indication of a security vulnerability, exploit, or active threat associated with this repository or account.
CVE-2026-76650 is a NULL pointer dereference vulnerability in the UPnP service of TP-Link TL-WR841N v14. It occurs when processing SOAP state variable query requests, potentially causing the UPnP service process to terminate unexpectedly or become unstable. Exploitation results in a denial-of-service condition affecting UPnP discovery and management functions until the process is restarted or the device rebooted. The vulnerability has a medium severity rating with a CVSS score of 5.3. No patch or official remediation guidance is currently available.
This analysis discusses the emerging threat posed by quantum computing to current public-key cryptographic algorithms such as RSA, ECC, and Diffie-Hellman. Although fully capable quantum computers are not yet available, adversaries are already collecting encrypted data to decrypt later once quantum capabilities mature, a tactic known as "harvest now, decrypt later" (HNDL). Regulatory bodies, including the U.S. government via Executive Order 14412, are mandating accelerated migration to quantum-resistant cryptography and require comprehensive cryptographic inventories. The transition to post-quantum cryptography involves a phased operational strategy including discovery, prioritization, remediation, and verification. Symmetric encryption like AES-256 is expected to remain secure against quantum attacks. The threat is recognized as an operational risk today, necessitating proactive organizational measures.
This report discusses how artificial intelligence is accelerating the discovery of software vulnerabilities, increasing pressure on existing systems designed to manage and remediate these flaws. It highlights the growing need for defenders to integrate multiple intelligence sources and improve the speed of vulnerability remediation to keep pace with AI-driven discovery. The content is an analysis of trends in vulnerability research rather than a specific vulnerability or exploit.
DaemonCore Linux is a Debian 13–based Linux distribution designed for authorized penetration testing, defensive security, incident response, forensics, and cybersecurity education. It includes a lightweight XFCE desktop, live USB boot with optional persistence, and a graphical installer. The distribution comes preloaded with a curated set of security tools for network discovery, wireless security, service assessment, web application testing, password auditing, forensics, reverse engineering, and development. Security defaults include a non-root live session, enabled firewall, disabled unnecessary network services, and common privilege escalation protections. The project is currently in early development and not yet a stable release. It is intended only for use on systems and networks with explicit authorization for testing.
A vulnerability in the complexQueryFilterSubprocess function of the NRF Discovery service in free5gc v4.0.1 allows attackers to cause a Denial of Service (DoS) via crafted input. This flaw does not impact confidentiality or integrity but can disrupt service availability.
Multiple ClickFix malware campaigns have been identified using three delivery methods: MSI packages with DLL sideloading, NodeJS-executed JavaScript, and Python 3.5 payload execution. These campaigns use aggressive social engineering, including phone calls directing victims to compromised WordPress sites. Post-compromise activities include extensive system discovery and Active Directory enumeration. The campaigns share infrastructure and tactics linked to the Lorem Ipsum malware family and Vanilla Tempest adversary, with potential ransomware deployment as a final goal.
This content discusses the evolving threat landscape shaped by artificial intelligence accelerating vulnerability discovery and exploit development. AI has drastically shortened the window between vulnerability disclosure and exploitation, often enabling attackers to weaponize flaws before patches are available. Traditional vulnerability management programs, which rely on slower patch cycles, are increasingly ineffective. The attack surface is also expanding with AI components introducing new classes of vulnerabilities not covered by conventional scanning tools. The briefing cited recommends rapid, risk-driven patching, improved dependency management, and leveraging AI for proactive defense. It emphasizes that AI-accelerated attacks represent a lasting shift requiring security programs to adapt for speed and prioritization.
A supply-chain attack compromised the maintainer account of the popular Rust crate arrayref, introducing malware that executed during compilation. The attacker also poisoned two other crates, append-only-vec and internment, within a short window. The malicious code included a typosquatted dependency that executed a payload tailored to the host OS, capable of stealing credentials and establishing persistence. The attack affected widely used Rust projects, including cryptography and blockchain tools. The compromised versions were quickly removed from the registry after discovery. Developers who used these versions during the exposure window should assume compromise and take remediation steps.
The action taken by OpenAI comes in light of the Hugging Face incident and the discovery of the Astra model’s advanced capabilities. The post OpenAI Overhauls Model Security With Sandboxing, 30-Minute Alerts, and Training Pauses appeared first on SecurityWeek .
NVIDIA Cumulus Linux contains a vulnerability in the Link Layer Discovery Protocol (LLDP) daemon component, where an unauthenticated attacker on an adjacent network could cause buffer overflow by sending crafted LLDP frames. A successful exploit of this vulnerability might lead to code execution.
In the Linux kernel, the following vulnerability has been resolved: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race Commit fbefe22811c3 ("scsi: libsas: Don't always drain event workqueue for HA resume") introduced sas_resume_ha_no_sync() to avoid a deadlock: the PHYE_RESUME_TIMEOUT handler, running on the HA event workqueue, calls sas_deform_port() -> sas_destruct_devices(), which removes SCSI devices and waits for the host to become runtime-active. But the host cannot resume until sas_resume_ha() -> sas_drain_work() returns, and the drain is blocked on that very handler. However skipping the drain reintroduces a race: hisi_sas returns from resume before all PHY UP work and libsas discovery work finish. The controller may then autosuspend while disks are still waking up. The disks issue IO to a suspended controller, the IO fails, and the disks get disabled. Fix the deadlock at its source by moving the PHYE_RESUME_TIMEOUT notification to after sas_drain_work(). By then the host resume is about to complete, so device removal through device_link no longer blocks on the resume and the cycle is broken. With the deadlock gone, restore sas_resume_ha() (the draining variant) in hisi_sas and remove sas_resume_ha_no_sync(). The reorder is safe for the other libsas consumers (isci, pm8001, aic94xx, mvsas). During suspend, sas_suspend_devices() calls sas_notify_lldd_dev_gone() for each device, which sets dev->lldd_dev to NULL. When scsi_unblock_requests re-enables I/O in resume, any I/O to a timed-out phy's disk is immediately rejected by the LLDD before reaching hardware: isci returns SAS_DEVICE_UNKNOWN (mapped to DID_BAD_TARGET), and pm8001 returns SAS_PHY_DOWN (mapped to DID_NO_CONNECT). Both complete directly via scsi_done() without entering SCSI EH. This is identical in both the old and new ordering since lldd_dev_gone runs during suspend, before resume. The reorder only affects when the PHYE_RESUME_TIMEOUT handler runs (synchronized by sas_drain_work() vs. asynchronous after resume returns), not whether I/O can reach the device. aic94xx and mvsas do not register any PM ops and never reach this code path.