A vulnerability was found in Greenshift Plugin up to 12.8.5 on WordPress and classified as problematic. This affects the function _gspb_post_css of the component Block Attribute Handler. Executing a manipulation can lead to cross site scripting.
This vulnerability is tracked as CVE-2026-2593. The attack can be launched remotely. No exploit exists.
A vulnerability has been found in Greenshift Plugin up to 12.8.3 on WordPress and classified as problematic. The impacted element is an unknown function of the component Setting Handler. Performing a manipulation results in information disclosure.
This vulnerability is identified as CVE-2026-2589. The attack can be initiated remotely. There is not any exploit available.
A vulnerability, which was classified as problematic, was found in Huawei HarmonyOS 5.1.0/6.0.0. The affected element is an unknown function of the component Device Security Management Module. Such manipulation leads to race condition.
This vulnerability is referenced as CVE-2026-28551. The attack can only be performed from a local environment. No exploit is available.
A vulnerability, which was classified as critical, has been found in Huawei HarmonyOS and EMUI. Impacted is an unknown function. This manipulation causes improper privilege management.
The identification of this vulnerability is CVE-2026-28548. The attack can only be executed locally. There is no exploit available.
A vulnerability classified as problematic was found in Huawei HarmonyOS and EMUI. This issue affects some unknown processing of the component System Service. The manipulation results in handling of exceptional conditions.
This vulnerability was named CVE-2026-28542. The attack needs to be approached locally. There is no available exploit.
A vulnerability classified as problematic has been found in Huawei HarmonyOS 5.1.0/6.0.0. This vulnerability affects unknown code of the component Maintenance Module. The manipulation leads to race condition.
This vulnerability is uniquely identified as CVE-2026-28543. Local access is required to approach this attack. No exploit exists.
A vulnerability described as critical has been identified in Huawei HarmonyOS 5.1.0/6.0.0. This affects an unknown part of the component cellular_data Module. Executing a manipulation can lead to improper access controls.
This vulnerability is handled as CVE-2026-28541. It is possible to launch the attack on the local host. There is not any exploit available.
A vulnerability marked as problematic has been reported in Huawei HarmonyOS 5.1.0/6.0.0. Affected by this issue is some unknown functionality of the component Data Handler. Performing a manipulation results in data processing error.
This vulnerability is known as CVE-2026-28539. Attacking locally is a requirement. No exploit is available.
A vulnerability labeled as problematic has been found in Huawei HarmonyOS 5.1.0/6.0.0. Affected by this vulnerability is an unknown functionality. Such manipulation leads to improper neutralization of null byte or nul character.
This vulnerability is traded as CVE-2026-28540. An attack has to be approached locally. There is no exploit available.
A vulnerability identified as problematic has been detected in Huawei HarmonyOS 5.1.0/6.0.0. Affected is an unknown function of the component Certificate Management Module. This manipulation causes path traversal: '../filedir'.
This vulnerability appears as CVE-2026-28538. The attack requires local access. There is no available exploit.
A vulnerability categorized as critical has been discovered in Huawei HarmonyOS 6.0.0. This impacts an unknown function of the component Scanning Module. The manipulation results in uninitialized pointer.
This vulnerability is reported as CVE-2026-28547. The attack requires a local approach. No exploit exists.
A vulnerability was found in Huawei HarmonyOS 6.0.0. It has been rated as problematic. This affects an unknown function of the component Permission Management Service. The manipulation leads to race condition.
This vulnerability is documented as CVE-2026-28549. The attack needs to be performed locally. There is not any exploit available.
Some weeks in cybersecurity feel routine. This one doesn’t.
Several new developments surfaced over the past few days, showing how quickly the threat landscape keeps shifting. Researchers uncovered fresh activity, security teams shared new findings, and a few unexpected moves from major tech companies also drew attention.
Together, these updates offer a useful snapshot of what is happening
A vulnerability was found in Huawei HarmonyOS 6.0.0. It has been declared as critical. The impacted element is an unknown function of the component Scanning Module. Executing a manipulation can lead to heap-based buffer overflow.
This vulnerability is registered as CVE-2026-28546. The attack needs to be launched locally. No exploit is available.
A vulnerability was found in Huawei HarmonyOS and EMUI. It has been classified as problematic. The affected element is an unknown function of the component IMS Module. Performing a manipulation results in data processing error.
This vulnerability is cataloged as CVE-2026-28552. It is possible to initiate the attack remotely. There is no exploit available.
A vulnerability was found in Huawei HarmonyOS 6.0.0 and classified as problematic. Impacted is an unknown function of the component Security Control Module. Such manipulation leads to business logic errors.
This vulnerability is listed as CVE-2026-28550. The attack must be carried out locally. There is no available exploit.
A vulnerability has been found in Huawei HarmonyOS 6.0.0 and classified as problematic. This issue affects some unknown processing of the component Printing Module. This manipulation causes race condition.
This vulnerability is tracked as CVE-2026-28545. The attack is restricted to local execution. No exploit exists.
A vulnerability, which was classified as problematic, was found in Huawei HarmonyOS 6.0.0. This vulnerability affects unknown code of the component Printing Module. The manipulation results in race condition.
This vulnerability is identified as CVE-2026-28544. The attack is only possible with local access. There is not any exploit available.