CVE-2026-88344

dvidelabs · flatcc

An out-of-bounds read vulnerability in the flatcc schema lexer allows for a heap buffer over-read when processing specifically crafted schema files, leading to an application crash.

Executive summary

An out-of-bounds read vulnerability in the flatcc schema lexer exposes applications to potential denial of service attacks via maliciously crafted schema files.

Vulnerability

The vulnerability exists in the schema lexer, where an integer digit-scan loop in the lex() function fails to validate input boundaries correctly. This flaw allows an unauthenticated attacker to trigger a heap buffer over-read by providing a schema buffer that ends with a digit.

Business impact

Successful exploitation of this vulnerability results in an application crash, causing a denial of service for systems relying on the flatcc library. Given the CVSS score of 7.5, the high severity reflects the ease of remote exploitation without authentication, which could disrupt critical business processes dependent on data serialization.

Remediation

Immediate Action: Monitor the official flatcc GitHub repository for release updates and apply the fix associated with commit c1dcc8ecd1a74b1e9e724ec7dc98828a5c95528e as soon as it is packaged in a stable release.

Proactive Monitoring: Review application logs for unexpected crashes or error patterns occurring during the ingestion or parsing of FlatBuffers schema files.

Compensating Controls: Implement strict input validation or sandboxing for any service that processes untrusted schema files to prevent the submission of malicious input to the parser.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Organizations utilizing the flatcc library should prioritize updating their software once a formal patch version is released by the maintainers. Given the potential for remote denial of service, administrators should evaluate their exposure to untrusted schema input and implement appropriate input filtering until a permanent fix is integrated into their production environment.

History

CVE Brief tracked this CVE 1 day before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 7.5 (3.1) from cvelistV5
  4. Analyst report written

Sources