CVE-2025-46732
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 · uneditedOpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to version 6.6.6, an IDOR vulnerability in the GrapQL `NotificationLineNotificationMarkReadMutation` and `NotificationLineNotificationDeleteMutation` mutations of OpenCTI allows an authenticated user to change the read status of a notification or delete a notification of another user in case he has knowledge of the UUID of the notification. When changing the read status of a notification, the user also receives the content of the notification they changed the read status of. Authenticated Users in OpenCTI can read, modify and delete notification of other users if they know the UUID of the notification. Version 6.6.6 fixes the issue.
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 confidenceIDOR vulnerability in OpenCTI's GraphQL API where the NotificationLineNotificationMarkReadMutation and NotificationLineNotificationDeleteMutation mutations lack proper ownership validation, allowing any authenticated user to modify or delete notifications belonging to other users by knowing their UUID. The vulnerability also exposes notification content when changing read status.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.6.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenCTI installationCheck if OpenCTI is running in your environment by querying running containers, processes, or services listening on common OpenCTI ports (4000 is default GraphQL port)Affected if OpenCTI is running and accessible via network
-
Determine installed OpenCTI versionCheck the OpenCTI version by inspecting the container image tag, docker-compose.yml version field, or querying the GraphQL API /api/system info endpoint for the 'version' fieldAffected if The version is lower than 6.6.6 (e.g., 6.6.5, 6.6.4, etc.)
-
Confirm GraphQL API accessibilityVerify the GraphQL endpoint is reachable at /graphql by sending a POST request with a basic introspection query or checking if port 4000 is openAffected if The GraphQL API is exposed and accepts authenticated requests
-
Check notification module usageQuery the GraphQL API to list notifications using the user token to see if any notifications exist in the systemAffected if Notifications exist in the system and can be queried via the authenticated API
-
Test notification mutation authorization (optional manual check)If you have access to two test accounts, query notifications to obtain a UUID from another user's notification, then attempt to mark it as read or delete it using the NotificationLineNotificationMarkReadMutation or NotificationLineNotificationDeleteMutation with that UUIDAffected if The mutation succeeds without returning an authorization error, indicating the vulnerability is present
Your environment is affected if OpenCTI is running with a version lower than 6.6.6 and the GraphQL API is accessible to authenticated users, as they could exploit the IDOR to access or manipulate other users' notifications.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.6.6
Upgrade OpenCTI to version 6.6.6 or later which implements proper authorization checks on notification mutations.
6.6.6
- Identify the current OpenCTI version in use
- Plan and schedule an upgrade to version 6.6.6
- Follow the official OpenCTI upgrade documentation to update to version 6.6.6
- Verify the upgrade by checking the OpenCTI version number after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46732 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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