CVE-2026-32939 Vulnerability Analysis & Exploit Details

CVE-2026-32939
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-32939 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-32939 Details

Status: Analyzed

Last updated: 🕖 23 Mar 2026, 19:25 UTC
Originally published on: 🕓 20 Mar 2026, 04:16 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2026-32939 Vulnerability Summary

CVE-2026-32939: DataEase is an open source data visualization analysis tool. Versions 2.10.19 and below have inconsistent Locale handling between the JDBC URL validation logic and the H2 JDBC engine's internal parsing. DataEase uses String.toUpperCase() without specifying an explicit Locale, causing its security checks to rely on the JVM's default runtime locale, while H2 JDBC always normalizes URLs using Locale.ENGLISH. In Turkish locale environments (tr_TR), Java converts the lowercase letter i to İ (dotted capital I) instead of the standard I, so a malicious parameter like iNIT becomes İNIT in DataEase's filter (bypassing its blacklist) while H2 still correctly interprets it as INIT. This discrepancy allows attackers to smuggle dangerous JDBC parameters past DataEase's security validation, and the issue has been confirmed as exploitable in real DataEase deployment scenarios running under affected regional settings. The issue has been fixed in version 2.10.20.

Assessing the Risk of CVE-2026-32939

Access Complexity Graph

The exploitability of CVE-2026-32939 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-32939

CVE-2026-32939 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-32939, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-32939, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-32939 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-32939 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-32939 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-32939 References

External References

CWE Common Weakness Enumeration

CWE-178

Vulnerable Configurations

  • cpe:2.3:a:dataease:dataease:-:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:-:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.11.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.11.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.11.3:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.11.3:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.13.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.13.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.15.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.15.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.15.3:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.15.3:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.15.4:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.15.4:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.17.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.17.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.3:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.3:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.4:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.4:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.5:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.5:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.6:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.6:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.7:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.7:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.8:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.8:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.9:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.9:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.10:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.10:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.11:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.11:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.12:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.12:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.13:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.13:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.14:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.14:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.15:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.15:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.16:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.16:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.17:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.17:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.18:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.18:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.19:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.19:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.20:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.20:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.21:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.21:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.22:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.22:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.23:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.23:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.24:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.24:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.25:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.25:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.26:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.26:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:1.18.27:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:1.18.27:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.2:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.3:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.3:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.4:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.4:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.6:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.6:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.8:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.8:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.9:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.9:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.10:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.10:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.11:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.11:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.12:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.12:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.13:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.13:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.14:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.14:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.15:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.15:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.16:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.16:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.17:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.17:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.18:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.18:*:*:*:*:*:*:*
  • cpe:2.3:a:dataease:dataease:2.10.19:*:*:*:*:*:*:*
    cpe:2.3:a:dataease:dataease:2.10.19:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-32939: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-5462 – A vulnerability was identified in Wahoo Fitness SYSTM App up to 7.2.1 on Android. Impacted is an unknown function of the file com/WahooFitness/SYST...
  • CVE-2026-4350 – The Perfmatters plugin for WordPress is vulnerable to arbitrary file deletion via path traversal in all versions up to, and including, 2.5.9.1. Thi...
  • CVE-2025-7024 – Incorrect Default Permissions vulnerability in AIRBUS PSS TETRA Connectivity Server on Windows Server OS allows Privilege Abuse. An attacker may ...
  • CVE-2026-5458 – A weakness has been identified in Noelse Individuals & Pro App up to 2.1.7 on Android. This impacts an unknown function of the file com/reactnative...
  • CVE-2026-5457 – A security flaw has been discovered in PropertyGuru AgentNet Singapore App up to 23.7.10 on Android. This affects an unknown function of the file c...