A security vulnerability (CVE-2026-25679) affecting the Grafana plugin for Performance Co-Pilot in Red Hat Enterprise Linux 8.4 has been addressed. The issue involves incorrect parsing of IPv6 host literals in the net/url package. Red Hat has released an important security update to fix this flaw in the grafana-pcp package for affected Red Hat Enterprise Linux 8.4 variants.
SKYSEA Client View and SKYMEC IT Manager provided by Sky Co.,LTD.configure the installation folder with improper file access permission settings. A non-administrative user may manipulate and/or place arbitrary files within the installation folder of the product. As a result, arbitrary code may be executed with the administrative privilege.
CVE-2026-5397 is a high-severity vulnerability in OMRON SOCIAL SOLUTIONS CO. , Ltd. 's PowerAttendant Standard Edition (version 2.1.2 or lower). The issue arises from improper permissions on the installation directory, allowing an attacker with local access to place a malicious DLL. This DLL may be loaded and executed with administrator privileges during the service startup due to the product's behavior of loading missing DLLs from its installation directory. No official patch or remediation guidance is currently available from the vendor. The vulnerability has not been reported as exploited in the wild.
Weaver (Fanwei) E-cology 10.0 versions prior to 20260312 contain an unauthenticated remote code execution vulnerability in the /papi/esearch/data/devops/dubboApi/debug/method endpoint that allows attackers to execute arbitrary commands by invoking exposed debug functionality. Attackers can craft POST requests with attacker-controlled interfaceName and methodName parameters to reach command-execution helpers and achieve arbitrary command execution on the system. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-03-31 (UTC).
An out-of-bounds read vulnerability exists in FUJI ELECTRIC CO. , LTD. / Hakko Electronics Co. , Ltd. V-SFT versions 6.2.10.0 and prior. The flaw occurs in the VS6ComFile component's get_macro_mem_COM function. Opening a specially crafted V7 file may cause information disclosure from the affected product.
An out-of-bounds read vulnerability exists in FUJI ELECTRIC CO. , LTD. / Hakko Electronics Co. , Ltd. V-SFT versions 6.2.10.0 and earlier. The flaw occurs in the function VS6MemInIF! set_temp_type_default and can be triggered by opening a specially crafted V7 file.
V-SFT versions 6.2.10.0 and earlier contain an out-of-bounds read vulnerability in the VS6ComFile! load_link_inf function. This vulnerability can be triggered by opening a specially crafted V7 file, potentially leading to information disclosure. The vulnerability has a high severity rating with a CVSS score of 7.8. There is no information provided about an available patch or vendor advisory. The product is not a cloud service, and no known exploits are reported in the wild.
V-SFT versions 6.2.10.0 and earlier contain a stack-based buffer overflow vulnerability in the VS6ComFile! CV7BaseMap::WriteV7DataToRom function. This flaw can be triggered by opening a specially crafted V7 file, potentially allowing an attacker to execute arbitrary code on the affected system. The vulnerability has a high severity rating with a CVSS score of 7.8. No official patch or vendor advisory information is provided at this time, and there are no known exploits in the wild.
Blind server-side request forgery (SSRF) vulnerability in legacy connection methods of document co-authoring features in M-Files Server before 26.3 allow an unauthenticated attacker to cause the server to send HTTP GET requests to arbitrary URLs.
This analysis examines multiple data leaks attributed to BreachForums between 2022 and 2026, focusing on distinguishing between leak publication dates and actual data timelines. The study covers four datasets associated with different domain names (.vc, .co, .hn, .bf) used by the platform. Each dataset is analyzed based on publication date, format, database structure, and the 'lastactive' field in the user table. The analysis reveals that the domain associated with a leak does not necessarily indicate the timing of the compromise, but rather the context of data collection. The article emphasizes the importance of differentiating between publication date and actual data timeline to avoid misattribution in cyber threat intelligence activities.