Local memory corruption via undisclosed stack overflow
Published Feb 25, 2026 · Updated Feb 25, 2026
Stack-based buffer overflow in CodeAstro Food Ordering System 1.0 allows local users to corrupt process memory via local input. The affected locus is an undisclosed function in food_ordering.exe; neither the CNA record nor its surviving references identifies the input field or unsafe copy operation. Low-privileged local access is required, no user interaction is reported, and published assessments do not confirm code execution or privilege escalation.
Summary
What happened
Stack-based buffer overflow in CodeAstro Food Ordering System 1.0 allows local users to corrupt process memory via local input. The affected locus is an undisclosed function in food_ordering.exe; neither the CNA record nor its surviving references identifies the input field or unsafe copy operation. Low-privileged local access is required, no user interaction is reported, and published assessments do not confirm code execution or privilege escalation.
The record
- CVE
- CVE-2026-3137
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- Winston D'Souza
- Product
- Food Ordering System in C Programming
- Classifications
- CWE-787, CWE-119, CWE-121
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- 910biter cve issue 3proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo