dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-66223

HIGH · 8.4 CVSS v4.0 Published 2025-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenObserve is a cloud-native observability platform. Prior to version 0.16.0, organization invitation tokens do not expire once issued, remain valid even after the invited user is removed from the organization, and allow multiple invitations to the same email with different roles where all issued links remain valid simultaneously. This results in broken access control where a removed or demoted user can regain access or escalate privileges. This issue has been patched in version 0.16.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenObserve versions before 0.16.0 have broken access control in the organization invitation system where invitation tokens never expire, remain valid after the invited user is removed from the organization, and allow multiple simultaneous invitations to the same email with different roles. This enables removed or demoted users to regain access or escalate privileges by using old invitation links.

MitigationUpgrade to version 0.16.0 or later which implements token expiration and invalidation logic for organization invitations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenObserve version
    Check the running OpenObserve instance version via the UI, API (e.g., GET /api/version), or container/container orchestration metadata. Compare the version number to the 0.16.0 threshold.
    Affected if The installed version is below 0.16.0 (e.g., 0.15.x, 0.14.x, etc.)
  2. Verify organization invitation feature is in use
    Query the database or API to list active organization invitations (e.g., GET /api/organizations/{org_id}/invitations or inspect the invitations table). Determine if any invitations exist.
    Affected if The organization invitation feature is actively used and there are pending or historical invitations in the system.
  3. Check for dangling invitations
    Review the invitation list to identify invitations for users who have since been removed from the organization. Cross-reference invitation records against current organization member list.
    Affected if Invitations exist for emails associated with users who are no longer members of the organization.
  4. Check for duplicate email invitations with different roles
    Query the invitation records to identify cases where the same email address appears multiple times with different role assignments.
    Affected if The same email address has multiple active invitations with different roles.

If OpenObserve version is below 0.16.0 AND the organization invitation system is in use with active or historical invitations, the environment is affected by this broken access control flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.16.0 or later which implements token expiration and invalidation logic for organization invitations.

Recommended fix High confidence

0.16.0

  1. Identify the current OpenObserve version in use (e.g., check deployment manifests, Docker tags, or running service version)
  2. Plan downtime or service restart as required by the deployment method
  3. Upgrade OpenObserve to version 0.16.0 or later
  4. Verify the upgrade was successful by checking the version number
  5. Test invitation functionality: create a new invitation, verify it expires as expected, and ensure previously issued invitations are invalidated or properly handled
Caveat Review release notes for 0.16.0 to check for any breaking changes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66223 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data