VulDB Recent Entries

A vulnerability was found in HCL AION 2.0. It has been rated as problematic. Affected is an unknown function of the component Content-Security-Policy Header Handler. The manipulation leads to protection mechanism failure. This vulnerability is uniquely identified as CVE-2025-52635. The attack is possible to be carried out remotely. No exploit exists.

A vulnerability was found in HCL AION 2.0. It has been declared as problematic. This impacts an unknown function. Executing manipulation can lead to information disclosure. This vulnerability is handled as CVE-2025-52630. The attack can be executed remotely. There is not any exploit available.

A vulnerability was found in HCL AION 2.0. It has been classified as critical. This affects an unknown function of the component Content-Security-Policy Header Handler. Performing manipulation results in protection mechanism failure. This vulnerability is known as CVE-2025-52624. Remote exploitation of the attack is possible. No exploit is available.

A vulnerability was found in HCL AION 2.0 and classified as problematic. The impacted element is an unknown function of the component Cacheable SSL Page Handler. Such manipulation leads to use of web browser cache containing sensitive information. This vulnerability is traded as CVE-2025-52625. The attack may be launched remotely. There is no exploit available.

A vulnerability has been found in Elastic Elasticsearch up to 7.17.29/8.18.7/8.19.4/9.0.7/9.1.4 and classified as problematic. The affected element is an unknown function of the component Reindex API. This manipulation causes sensitive information in log files. This vulnerability appears as CVE-2025-37727. The attacker needs to be present on the local network. There is no available exploit.

A vulnerability, which was classified as critical, was found in Fuji Electric V-SFT up to 6.2.7.0. Impacted is the function get_ovlp_element_size of the component V-SFT File Parser. The manipulation results in out-of-bounds read. This vulnerability is reported as CVE-2025-61862. The attack can be launched remotely. No exploit exists.

A vulnerability, which was classified as problematic, has been found in Fuji Electric V-SFT up to 6.2.7.0. This issue affects the function load_link_inf of the component V-SFT File Parser. The manipulation leads to out-of-bounds read. This vulnerability is documented as CVE-2025-61861. The attack can be initiated remotely. There is not any exploit available.

A vulnerability classified as critical was found in Fuji Electric V-SFT up to 6.2.7.0. This vulnerability affects the function set_temp_type_default of the component V-SFT File Parser. Executing manipulation can lead to out-of-bounds read. This vulnerability is registered as CVE-2025-61860. It is possible to launch the attack remotely. No exploit is available.

A vulnerability classified as critical has been found in Fuji Electric V-SFT up to 6.2.7.0. This affects the function CItemDraw::is_motion_tween of the component V-SFT File Parser. Performing manipulation results in out-of-bounds write. This vulnerability is cataloged as CVE-2025-61859. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability described as critical has been identified in Fuji Electric V-SFT up to 6.2.7.0. Affected by this issue is the function set_AnimationItem of the component V-SFT File Parser. Such manipulation leads to out-of-bounds write. This vulnerability is listed as CVE-2025-61858. The attack may be performed from remote. There is no available exploit.

A vulnerability marked as critical has been reported in Fuji Electric V-SFT up to 6.2.7.0. Affected by this vulnerability is the function CItemExChange::WinFontDynStrCheck of the component V-SFT File Parser. This manipulation causes out-of-bounds write. This vulnerability is tracked as CVE-2025-61857. The attack is possible to be carried out remotely. No exploit exists.

A vulnerability labeled as critical has been found in Fuji Electric V-SFT up to 6.2.7.0. Affected is the function CV7BaseMap::WriteV7DataToRom of the component V-SFT File Parser. The manipulation results in stack-based buffer overflow. This vulnerability is identified as CVE-2025-61856. The attack can be executed remotely. There is not any exploit available.

A vulnerability identified as problematic has been detected in HCL MyXalytics 6.6. This impacts an unknown function. The manipulation leads to inclusion of functionality from untrusted control sphere. This vulnerability is referenced as CVE-2025-52655. Remote exploitation of the attack is possible. No exploit is available.

A vulnerability categorized as problematic has been discovered in Status Tracker Energy CRM 2025. This affects an unknown function of the file /crm/create_invoice_submit.php of the component Query Handler. Executing manipulation of the argument customerName_0 can lead to cross site scripting. The identification of this vulnerability is CVE-2025-40640. The attack may be launched remotely. There is no exploit available.

A vulnerability was found in Samsung Devices. It has been rated as problematic. The impacted element is an unknown function of the component Contacts. Performing manipulation results in information disclosure. This vulnerability was named CVE-2025-21050. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised.

A vulnerability was found in Google Go up to 1.25.1. It has been declared as problematic. The affected element is an unknown function of the component crypto-x509. Such manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2025-58187. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.

A vulnerability was found in Google Go up to 1.25.1. It has been classified as problematic. Impacted is an unknown function of the component net-http. This manipulation causes uncontrolled memory allocation. This vulnerability is handled as CVE-2025-58186. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

A vulnerability was found in Google Go up to 1.25.1 and classified as problematic. This issue affects the function Reader.ReadResponse of the component net-textproto. The manipulation results in resource consumption. This vulnerability is known as CVE-2025-61724. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.

A vulnerability, which was classified as problematic, was found in Google Go up to 1.25.1. This affects an unknown part of the component archive-tar. Executing manipulation can lead to allocation of resources. This vulnerability appears as CVE-2025-58183. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.

A vulnerability has been found in Google Go up to 1.25.1 and classified as critical. This vulnerability affects unknown code of the component crypto-tls. The manipulation leads to injection. This vulnerability is traded as CVE-2025-58189. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.