Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-27507: IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: zitadel zitadel 2.71.0.

Low priority for now. Upgrade to zitadel zitadel 2.71.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. ZITADEL's Admin API contains Insecure Direct Object Reference (IDOR) vulnerabilities that allow authenticated users, without specific IAM roles, to modify sensitive settings. While several endpoints are affected, the most critical vulnerability lies in the ability to manipulate LDAP configurations. Customers who do not utilize LDAP for authentication are not at risk from the most severe aspects of this vulnerability. However, upgrading to the patched version to address all identified issues is strongly recommended. This vulnerability is fixed in 2.71.0, 2.70.1, ,2.69.4, 2.68.4, 2.67.8, 2.66.11, 2.65.6, 2.64.5, and 2.63.8.

CriticalCVSS 9.0 · v3.1—No exploit Fix available
Published
Mar 4, 2025
Updated
Jun 17, 2026
EPSS
0.6% · 49th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-27507

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for zitadel records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
zitadelzitadel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • zitadel zitadelbefore 2.63.8
  • zitadel zitadel2.64.0 and later · before 2.64.5
  • zitadel zitadel2.65.0 and later · before 2.65.6
  • zitadel zitadel2.66.0 and later · before 2.66.11
  • zitadel zitadel2.67.0 and later · before 2.67.8
  • zitadel zitadel2.68.0 and later · before 2.68.4
  • zitadel zitadel2.69.0 and later · before 2.69.4
  • zitadel zitadel2.70.0 and later · before 2.70.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • zitadel zitadel

    • >= 2.63.0-rc.1, < 2.63.8, >= 2.64.0-rc.1, < 2.64.5, >= 2.66.0-rc.1, < 2.66.11, >= 2.67.0-rc.1, < 2.67.8, >= 2.68.0-rc.1, < 2.68.4, >= 2.69.0-rc.1, < 2.69.4, >= 2.70.0-rc.1, < 2.70.1, >= 2.65.0-rc.1, < 2.65.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/zitadel/zitadelfrom 0—
Gogithub.com/zitadel/zitadelfrom 2.64.0 · before 2.64.52.64.5
Gogithub.com/zitadel/zitadelfrom 2.65.0 · before 2.65.62.65.6
Gogithub.com/zitadel/zitadelfrom 2.66.0 · before 2.66.112.66.11
Gogithub.com/zitadel/zitadelfrom 2.67.0 · before 2.67.82.67.8
Gogithub.com/zitadel/zitadelfrom 2.68.0 · before 2.68.42.68.4
Gogithub.com/zitadel/zitadelfrom 2.69.0 · before 2.69.42.69.4
Gogithub.com/zitadel/zitadelfrom 2.70.0 · before 2.70.12.70.1
Gogithub.com/zitadel/zitadelbefore 2.63.82.63.8
Gogithub.com/zitadel/zitadel/v2from 2.64.0 · before 2.64.52.64.5
Gogithub.com/zitadel/zitadel/v2from 2.65.0 · before 2.65.62.65.6
Gogithub.com/zitadel/zitadel/v2from 2.66.0 · before 2.66.112.66.11
Gogithub.com/zitadel/zitadel/v2from 2.67.0 · before 2.67.82.67.8
Gogithub.com/zitadel/zitadel/v2from 2.68.0 · before 2.68.42.68.4
Gogithub.com/zitadel/zitadel/v2from 2.69.0 · before 2.69.42.69.4
Gogithub.com/zitadel/zitadel/v2from 2.70.0 · before 2.70.12.70.1
Gogithub.com/zitadel/zitadel/v2before 2.63.82.63.8

Same product

zitadel: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-109372ZITADEL 3.0.0 before 4.19.2 Account Takeover via SAML Identity-Provider Confusion
    37Monitor
  • CVE-2026-105215ZITADEL before 4.16.2 Account Pre-Hijacking via Forged External IdP Callback
    37Monitor
  • CVE-2026-105209ZITADEL before 3.4.15 and 4.17.1 Cross-Organization Account Takeover via Passkey Enrollment
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-49753Oct 25, 2024 · Denied Host Validation Bypass in Zitadel Actions
    36Monitor
  • ← EarlierCVE-2024-49757Oct 25, 2024 · Zitadel User Registration Bypass Vulnerability
    20Monitor
  • Later →CVE-2025-31123Mar 31, 2025 · Zitadel Expired JWT Keys Usable for Authorization Grants
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
zitadel zitadel2.71.0 · descriptionVendor (CNA)
Go:github.com/zitadel/zitadel2.63.8Package registry (OSV)
Go:github.com/zitadel/zitadel2.64.5Package registry (OSV)
Go:github.com/zitadel/zitadel2.65.6Package registry (OSV)
Go:github.com/zitadel/zitadel2.66.11Package registry (OSV)
Go:github.com/zitadel/zitadel2.67.8Package registry (OSV)
Go:github.com/zitadel/zitadel2.68.4Package registry (OSV)
Go:github.com/zitadel/zitadel2.69.4Package registry (OSV)
Go:github.com/zitadel/zitadel2.70.1Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.63.8Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.64.5Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.65.6Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.66.11Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.67.8Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.68.4Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.69.4Package registry (OSV)
Go:github.com/zitadel/zitadel/v22.70.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-64431248 days apartIDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering
    34Monitor
  • CVE-2026-32131372 days apartZITADEL Cross-Tenant Information Disclosure in Management API
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

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

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const invoice = await Invoice.findById(req.params.id);res.json(invoice);

Fixed

ts
const invoice = await Invoice.findOne({  id: req.params.id,  ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records