CVE-2025-54603
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 · uneditedAn incorrect OIDC authentication flow in Claroty Secure Access 3.3.0 through 4.0.2 can result in unauthorized user creation or impersonation of existing OIDC users.
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 · moderate confidenceIncorrect OIDC authentication flow in Claroty Secure Access versions 3.3.0-4.0.2 allows unauthorized creation of users or impersonation of existing OIDC users, potentially granting attackers unauthorized access to the platform.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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.
-
Verify Claroty Secure Access versionAccess the product admin console or use the system information command (typically via CLI or web UI) to retrieve the installed version numberAffected if The installed version falls within the range 3.3.0 to 4.0.2 inclusive
-
Confirm OIDC authentication is configuredNavigate to the authentication settings in the Claroty Secure Access admin interface and verify if OpenID Connect (OIDC) identity provider integration is enabledAffected if OIDC authentication is enabled and the version is within the affected range
-
Review user creation audit logsAccess the platform audit logs or user management logs and search for user creation events, particularly those with timestamps or sources that are unexpectedAffected if There are user creation events that were not initiated by legitimate administrators
-
Inspect for unauthorized OIDC user accountsIn the user management panel, list all OIDC-provisioned users and compare against expected users from your identity provider; look for unknown or unexpected user accountsAffected if There are OIDC users present that do not correspond to authorized identity provider users
-
Check for duplicate or impersonated user accountsReview user accounts for duplicate entries, accounts with similar names to legitimate users, or accounts created in rapid successionAffected if Multiple accounts exist for the same identity provider user or suspicious account patterns are found
A user is affected if Claroty Secure Access version is between 3.3.0 and 4.0.2 inclusive AND OIDC authentication is enabled, with potential evidence of unauthorized user creation or user impersonation in logs or user directories.
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.
From vendor dataUpgrade Claroty Secure Access to a version beyond 4.0.2 and review OIDC configuration settings to ensure authentication flow integrity.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54603 — 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-54603 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