CVE-2026-90716
Deferred Deferred - Pending Action

Out-of-Bounds Read in Gravity Number Parser

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: VulDB

Description
A vulnerability was detected in marcobambini Gravity up to 0.9.7. This impacts the function parse_number_expression of the file src/compiler/gravity_parser.c of the component Number Parser. Performing a manipulation results in out-of-bounds read. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 0.9.8 will fix this issue. The patch is named 1b9bbf3ad5749e2a3434e6ad073c6e93c24207b6. It is recommended to upgrade the affected component.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-15
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
CVE-2026-90716
EUVD
EUVD-2026-77443

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
marcobambini gravity to 0.9.7 (inc)
marcobambini gravity 0.9.8
marcobambini gravity to 0.9.8 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-119 The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a heap out-of-bounds read vulnerability in the Gravity programming language's parser. It occurs in the parse_number_expression function when processing a number literal ending with a single '0'. The function checks for numeric prefixes like 0b, 0o, or 0x by reading the second character without verifying the token length, causing a 1-byte read past the buffer's end.

Detection Guidance

To detect this vulnerability, inspect Gravity installations for versions up to 0.9.7. Use commands like 'gravity --version' to check the version. Monitor for crashes when processing inputs ending with '0' (e.g., 'x=0'). Enable AddressSanitizer (ASan) during compilation to catch heap out-of-bounds reads.

Impact Analysis

The vulnerability can crash the program when detected by tools like AddressSanitizer. In production, it may leak data from adjacent memory if exact-size buffers are used. The impact is limited to a single byte read with no escalation path.

Compliance Impact

This vulnerability is a heap out-of-bounds read in the Gravity programming language's parser, which could lead to program crashes or potential data leaks. It does not directly impact compliance with GDPR or HIPAA, as those standards focus on data protection, privacy, and security controls rather than specific memory safety issues in programming language parsers.

Mitigation Strategies

Upgrade Gravity to version 0.9.8 or apply the patch 1b9bbf3ad5749e2a3434e6ad073c6e93c24207b6. Ensure all components using gravity_compiler_run or gravity_vm_loadbuffer with non-terminated buffers are updated. Avoid processing untrusted inputs ending with '0' until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-90716. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart