Skip to content
VulniPulse
Advisory severityLow2.1Apache Software Foundation Updated

Low [CVE-2026-78243] Apache YuniKorn 1.8.0 and later, if configured with the LDAP group resolver, crashes due to an out of bounds read processing group membership entries.If the LDAP server returns a group membership entry, memberOf attribute, for a user specified in the pod the server crashes if a membership record does not start with "CN="

This low-severity Apache Software Foundation advisory covers CVE-2026-78243; related products: Apache YuniKorn.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-78243 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Apache YuniKorn 1.8.0 and later, if configured with the LDAP group resolver, crashes due to an out of bounds read processing group membership entries.If the LDAP server returns a group membership entry, memberOf attribute, for a user specified in the pod the server crashes if a membership record does not start with "CN=".

This only affects install that have the non default LDAP group provider configured.

Users are recommended to upgrade to version 1.10.0, which fixes this issue.

Affected versions
  • Apache YuniKorn 1.8.0 before 1.10.0

Official advisory · high-confidence parse· fetched 17 hours ago·verify at source

Fixed versions
  • 1.10.0

Official advisory · high-confidence parse· fetched 17 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • This only affects install that have the non default LDAP group provider configured.
  • Users are recommended to upgrade to version 1.10.0, which fixes this issue.

Official advisory · high-confidence parse· fetched 17 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.