CVE-2026-57914
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 · uneditedBy sending a deeply nested ASN1 structure to a Apache Kerby client or service, it's possible to trigger a StackOverFlow Exception which can lead to denial of service issues. 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 contains a stack-based buffer overflow vulnerability in its ASN1 parsing logic. By sending a specially crafted, deeply nested ASN1 structure to a Kerby client or service, an attacker can trigger a StackOverflow Exception, causing the application to crash and resulting in denial of service.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 JAR files in application classpaths, lib directories, or check Maven/Gradle dependencies for org.apache.kerby:kerby-* packagesAffected if Apache Kerby is present in the environment
-
Determine installed versionExamine the kerby JAR file name, MANIFEST.MF within the JAR, or dependency management files to find the exact version numberAffected if Version is 2.1.1 or earlier (before the 2.1.2 fix)
-
Verify ASN1 parsing is enabledReview application configuration and code for ASN1 decoding operations, particularly when processing Kerberos tickets or GSSAPI tokensAffected if The application parses ASN1-encoded structures (required for the overflow to trigger)
-
Assess network accessibilityIdentify if Kerby-based services (KDC, Kadmin, or client endpoints) are exposed to network connections that could receive specially crafted ASN1 inputAffected if Kerby services accept untrusted network connections
If Apache Kerby version 2.1.1 or earlier is installed and configured to accept network ASN1 input, the environment is affected by this vulnerability
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 vulnerability. Consider implementing network-level controls to limit untrusted ASN1 input if immediate upgrade is not feasible.
2.1.2
- 1. Stop the Apache Kerby service if running
- 2. Obtain Apache Kerby version 2.1.2 from the official Apache distribution repositories (https://directory.apache.org/subversions.html)
- 3. Back up the existing Apache Kerby installation directory and configuration files
- 4. Replace the existing installation with version 2.1.2 files
- 5. Restore your configuration files from the backup (or reconfigure as needed)
- 6. Start the Apache Kerby service
- 7. Verify the service is functioning correctly and the vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57914 — 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-57914 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