CVE-2026-45080
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 · uneditedKlaw is a self-service Apache Kafka Topic Management/Governance tool/portal. Prior to version 2.10.4, improper access control allows disclosure of password hash. This issue has been patched in version 2.10.4.
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 confidenceKlaw versions prior to 2.10.4 contain an improper access control vulnerability that allows unauthorized users to access password hashes. This authentication bypass likely stems from missing or insufficient authorization checks on certain API endpoints or UI views, potentially exposing stored password hashes that could be subjected to offline cracking attacks.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Klaw versionLocate the Klaw version by checking the application UI (typically in About or Settings), the WAR/JAR file metadata, Docker image tag, or any version configuration file in the installation directoryAffected if The detected version is any release prior to 2.10.4 (e.g., 2.10.3, 2.10.0, 2.9.0, etc.)
-
Verify user access controls are in placeReview the Klaw user permission configuration to determine whether role-based access controls are properly configured and whether any user accounts have permissions that should be restrictedAffected if Users with limited or non-administrative roles exist and the Klaw version is prior to 2.10.4, indicating the improper access control vulnerability could allow unauthorized hash access
-
Inspect API endpoint access patternsReview Klaw API access logs or audit logs for any requests that retrieve user data, password hashes, or sensitive user-related endpoints made by non-admin usersAffected if Any non-administrative user account successfully accessed endpoints that return password hash data, combined with running a version prior to 2.10.4
A defender is affected if their installed Klaw version is any release prior to 2.10.4 and the application has user accounts with restricted permissions that should not have access to password hash data.
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 · scopedUpgrade Klaw to version 2.10.4 or later to apply the security patch. Additionally, consider rotating all user passwords as a precautionary measure given the potential exposure of password hashes.
Klaw version 2.10.4
- Upgrade Klaw to version 2.10.4 or later to address the improper access control vulnerability
- After upgrading, verify that user access controls are functioning correctly
- As a precaution, consider rotating any passwords that may have been stored in the system prior to the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45080 — 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-2026-45080 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