Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local code execution
-
DeliveryDeploy Ring 3 user process
-
ExploitInvoke Syscall 12 with kernel address
-
ExecutionExecute arbitrary code at Ring 0
-
ImpactInstall rootkit or exfiltrate data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires local code execution capability on a NovumOS system - the attacker must already run a Ring 3 user-mode process to invoke Syscall 12. CVSS vector PR:N indicates no authentication is required beyond the ability to execute user-mode code, meaning any process running in user space can trigger the vulnerability regardless of user account privileges. The system must be configured to support Ring 3 user-mode processes; workarounds specifically disable this to prevent exploitation. The vulnerability is NOT exploitable remotely (AV:L) - attackers need existing local access through another vector (application exploit, physical access, legitimate user account, or supply chain compromise of software running on NovumOS). Attack complexity is low (AC:L) with no special timing, race conditions, or complex setup required. UI:N confirms no user interaction beyond the attacker's own code execution. Exploitation is limited to x86-compatible hardware running NovumOS < 0.24 with user-mode processes enabled. |
| Impact | Real-world risk assessment reveals conflicting signals requiring careful interpretation. CVSS 9.3 (Critical) with AV:L/AC:L/PR:N reflects local attack vector with low complexity and no authentication barrier, paired with scope change (S:C) indicating privilege boundary escape from user to kernel mode. The PR:N (no privileges required) metric is technically accurate since any Ring 3 process can invoke syscalls, though this may mislead automated scanners - the attacker still needs local code execution to begin the attack chain. SSVC framework confirms POC availability and total technical impact (complete system compromise), but marks automatable:no due to the local-only nature. The contradiction emerges with EPSS: despite POC existence and critical CVSS, the 0.02% exploitation probability (5th percentile) suggests minimal real-world targeting. This discrepancy is explained by NovumOS being a niche custom operating system likely used in research, embedded systems, or specialized deployments rather than enterprise production environments. The vulnerability is severe for organizations actually running NovumOS - complete Ring 0 compromise is possible - but affects a limited user base. Defenders running this OS should treat as critical; organizations not using NovumOS can deprioritize. No CISA KEV listing confirms this is not being exploited in widespread attacks despite POC availability. |
| Exploit ScenarioDerived | An attacker with local code execution on a NovumOS system (for example, through a compromised user application or physical access to a terminal) writes a small Ring 3 user-mode program that invokes Syscall 12 with a crafted entry point address targeting kernel memory space. The syscall accepts the malicious address without validation and transfers execution to attacker-controlled shellcode now running at Ring 0 privilege. With kernel-level access, the attacker disables security mechanisms, installs persistent rootkits, exfiltrates sensitive data from kernel memory, or manipulates hardware directly. SSVC confirms POC code exists, lowering the technical barrier for attackers already possessing local access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Apr 27, 2026
Syscall 12 (JumpToUser) in NovumOS versions prior to 0.24 executes arbitrary kernel code at Ring 0 privilege when invoked by unprivileged Ring 3 user-mode processes. The vulnerability stems from missing address validation on user-supplied entry points, enabling local privilege escalation from user mode to kernel mode with complete system control. CISA SSVC framework confirms publicly available exploit code (POC status) with total technical impact, though EPSS score remains low at 0.02% (5th percentile), suggesting limited real-world targeting of this niche custom operating system despite the severe technical flaw.
Earlier versions of this analysis (2)
Unvalidated kernel entry point in NovumOS syscall 12 (JumpToUser) allows any Ring 3 user process to execute arbitrary code at Ring 0 (kernel) privilege level. Affects all versions before 0.24 of this custom x86 operating system written in Zig. The flaw enables complete local privilege escalation from user mode to kernel mode without authentication. CVSS 9.3 (Critical) reflects scope change from user to kernel context. No active exploitation confirmed (not in CISA KEV), EPSS data not available for this niche OS project.
Local privilege escalation in NovumOS (all versions before 0.24) allows unprivileged Ring 3 user-mode processes to execute arbitrary kernel code in Ring 0 context via unvalidated syscall parameters. Syscall 12 (JumpToUser) accepts arbitrary entry point addresses from user-space registers without validation, enabling direct jumps to kernel memory. Fixed in version 0.24 per vendor advisory. CVSS 9.4 (Critical) with scope change indicates container/VM escape potential. No public exploit identified at time of analysis, EPSS data unavailable.
RemediationAI
Upgrade immediately to NovumOS version 0.24 or later, available at https://github.com/MinecAnton209/NovumOS/releases/tag/v0.24, which implements address validation for Syscall 12 entry points. For environments unable to upgrade immediately, the vendor advisory recommends two compensating controls with significant operational impact: (1) Run the system in single-user mode without Ring 3 privilege level, effectively disabling all user-mode process execution - this eliminates the attack surface but removes multi-user functionality and application isolation. (2) Disable user-mode processes entirely by running only the kernel shell with no user processes - this reduces the OS to kernel-only operation, negating the purpose of ring separation. Both workarounds severely limit system utility and are only viable for development/testing environments or systems that can operate with kernel-only code. Production deployments should prioritize immediate patching to v0.24, as the workarounds fundamentally disable core OS functionality. Organizations should audit which systems run NovumOS (likely embedded devices, research platforms, or specialized controllers) and establish a patch timeline based on change control processes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
NovumOS is a custom 32-bit operating system implemented in Zig and x86 Assembly, employing x86 privilege ring architecture where Ring 0 represents kernel mode with unrestricted hardware access and Ring 3 represents user mode with limited privileges. The vulnerability resides in Syscall 12 (JumpToUser), a system call interface that transitions execution context between privilege levels. The root cause is improper privilege management (CWE-269) - specifically, the syscall accepts an arbitrary memory address from user-space CPU registers (likely EIP/instruction pointer) and performs an unconditional jump without validating whether the target address resides in kernel memory space. In x86 protected mode, kernel addresses typically occupy high memory regions (0xC0000000+ in many designs), while user-space is confined to lower addresses. By passing a kernel-space address through syscall parameters, an attacker bypasses ring separation and executes arbitrary instructions with kernel privileges.
Know when Novumos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
6DescriptionCVE.org
NovumOS is a custom 32-bit operating system written in Zig and x86 Assembly. In versions prior to 0.24, Syscall 12 (JumpToUser) accepts an arbitrary entry point address from user-space registers without validation, allowing any Ring 3 user-mode process to jump to kernel addresses and execute arbitrary code in Ring 0 context, resulting in local privilege escalation. This issue has been fixed in version 0.24. If developers are unable to immediately update, they should restrict syscall access by running the system in single-user mode without Ring 3, and disable user-mode processes by only running kernel shell with no user processes. This issue has been fixed in version 0.24.
Executive ViewAI
CVE-2026-40317 is a critical privilege escalation flaw in NovumOS prior to version 0.24 that allows local users to execute arbitrary code at kernel level, bypassing all OS-level security controls. Organizations running NovumOS must prioritize immediate patching, as any user with system access can gain complete administrative control; the low EPSS score reflects limited current targeting rather than reduced severity.
Apply vendor patch. Until patching is complete: restrict local system access to only trusted administrative personnel, disable unnecessary user accounts, implement host-based process monitoring for Ring 0 syscall anomalies, and isolate critical NovumOS systems from general user networks.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-23630
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB