CVE-2026-57915
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 · uneditedIt is possible to bypass the Kerberos pre-authentication check in Apache Kerby by sending a PA-DATA with an unrecognized or unsupported type. Users are recommended to upgrade to version 2.1.2, which fixes this 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 confidenceApache Kerby has a vulnerability where the Kerberos pre-authentication check can be bypassed by sending PA-DATA (Pre-Authentication Data) with an unrecognized or unsupported type. This allows an attacker to potentially authenticate without proper pre-authentication validation.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Identify Apache Kerby installationSearch for kerby-related JAR files, directories, or check if the Kerby service is running. Common locations include /opt/kerby, /usr/share/kerby, or application lib directories containing kerby-*.jar files.Affected if Apache Kerby is present in the environment
-
Determine installed Kerby versionCheck the version of kerby JAR files or the kerby-distribution. Look for version manifests, or run: java -jar kerby-*.jar --version. Compare the version against 2.1.2.Affected if Installed version is earlier than 2.1.2
-
Verify Kerberos pre-authentication is enforcedReview Kerby KDC configuration files (kdc.conf or kdc.json) for pre-authentication settings. Look for options like requirePreauth or paDataTypes to confirm pre-authentication is enabled and enforced.Affected if Pre-authentication is disabled or not properly configured in the KDC
-
Check KDC network exposureDetermine if the Kerby KDC service is exposed on the network. Review service bindings or firewall rules. The vulnerability is exploitable when the KDC accepts network requests from untrusted clients.Affected if KDC is network-accessible to untrusted clients
The environment is affected if Apache Kerby version earlier than 2.1.2 is installed and the KDC is configured to handle Kerberos authentication requests.
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 Apache Kerby to version 2.1.2 or later, which contains the fix for this pre-authentication bypass vulnerability.
2.1.2
- Upgrade Apache Kerby to version 2.1.2 to resolve the Kerberos pre-authentication bypass vulnerability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57915 — 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-57915 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