CVE-2026-13455 Vulnerability Analysis & Exploit Details

CVE-2026-13455
Vulnerability Scoring

4.3
/10
Medium Risk

The vulnerability CVE-2026-13455 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-13455 Details

Status: Analyzed

Last updated: 🕗 06 Jul 2026, 20:23 UTC
Originally published on: 🕓 30 Jun 2026, 16:16 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-13455 Vulnerability Summary

CVE-2026-13455: PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to repeatedly call the anon.hash() function and collects (seed, hash_output) pairs to perform an offline brute-force attack and deduce the salt. The problem is resolved in PostgreSQL Anonymizer 3.1.2 and later versions

Assessing the Risk of CVE-2026-13455

Access Complexity Graph

The exploitability of CVE-2026-13455 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-13455

CVE-2026-13455 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-13455, 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-13455, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-13455 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2026-13455 poses no threat to data integrity.
  • Availability: None
    CVE-2026-13455 does not impact system availability.

CVE-2026-13455 References

External References

CWE Common Weakness Enumeration

CWE-328

CAPEC Common Attack Pattern Enumeration and Classification

  • Web Services API Signature Forgery Leveraging Hash Function Extension Weakness CAPEC-461 An adversary utilizes a hash function extension/padding weakness, to modify the parameters passed to the web service requesting authentication by generating their own call in order to generate a legitimate signature hash (as described in the notes), without knowledge of the secret token sometimes provided by the web service.
  • Subvert Code-signing Facilities CAPEC-68 Many languages use code signing facilities to vouch for code's identity and to thus tie code to its assigned privileges within an environment. Subverting this mechanism can be instrumental in an attacker escalating privilege. Any means of subverting the way that a virtual machine enforces code signing classifies for this style of attack.

Vulnerable Configurations

  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.0.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.0.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.0.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.0.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.1.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.1.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.5.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.6.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.6.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.7.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.7.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.7.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.7.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.8.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.8.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.8.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.8.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.9.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.9.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.10.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.10.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.11.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.11.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:0.12.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:0.12.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:1.0.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:1.0.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:1.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:1.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:1.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:1.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:1.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:1.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:1.3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:1.3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:1.3.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:1.3.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:-:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:-:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:rc1:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:rc1:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:rc2:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:rc2:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:rc3:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:rc3:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta1:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta1:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta2:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta2:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta3:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta3:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta4:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:beta4:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:alpha1:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:alpha1:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:alpha2:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.0.0:alpha2:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.2.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.2.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.5.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:2.5.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:2.5.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.12:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.12:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.13:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.0.13:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.1.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.1.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:dalibo:postgresql_anonymizer:3.1.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:dalibo:postgresql_anonymizer:3.1.1:*:*:*:*:postgresql:*:*

Protect Your Infrastructure against CVE-2026-13455: 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-15928 – XMLRPC-C Library versions 1.07 through 1.67.01 are vulnerable to a reflected cross-site scripting (XSS) vulnerability in the error page component.
  • CVE-2026-17501 – A flaw has been found in ggml-org llama.cpp e15efe0. This vulnerability affects the function transform of the file common/json-schema-to-grammar.cp...
  • CVE-2026-17500 – A vulnerability was detected in ggml-org llama.cpp d006858/e15efe0. This affects the function _visit_pattern of the file common/json-schema-to-gram...
  • CVE-2026-57990 – Files or directories accessible to external parties in Microsoft Edge (Chromium-based) allows an unauthorized attacker to disclose information over...
  • CVE-2026-57989 – Origin validation error in Microsoft Edge (Chromium-based) allows an unauthorized attacker to disclose information over a network.