Advisories
Problems that are fixed and out in a build. Each says what was wrong, what changed, and the build to update to.
Scores are CVSS 3.1 base scores, and the severity follows the score.
Hardening: a defence made stronger where no way to exploit it is known, so it has no score.
An administrator's yes could be used for a different command
When an administrator said yes for a system task (installing, removing or updating a program, switching the update channel, removing update leftovers), Mizu let the next start of the package tool run as an administrator, whatever it was started to do, for up to a minute. A program that could get that start made first - the app that asked, or the desktop starting a program on another one's behalf - could use the yes for another package command, such as removing a package. Before build 182 the yes went to any program started next. A yes now counts only for the exact command it was given for, once, within 10 seconds. A start with anything else runs without an administrator's rights and leaves the yes for the right one. The box describes the command itself, not the asking app's words.
- Score
- CVSS 3.1 4.4
AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N
- Affects
- Accounts and permissions
- Found
- in build 178, by Claude (code review)
- Fixed
- in build 1344, 2026-11-20: update to build 1344 or later
- Published
- 2026-11-20
An administrator's work could leave system files that account could change without asking
When an administrator installed a program for everyone (after saying yes), the files Mizu wrote for the system at that moment - the machine's settings file, and the package records - became that administrator's own. From then on, programs that account ran without an administrator's yes could change them: the machine's settings, or a package record, which a later removal follows. Also, the file that keeps the event log could be read by every account, though the system hides the disks' identifiers in it from them. What an administrator makes in the system's own folders now belongs to the system, as do the settings Mizu rewrites. At the next start, Mizu gives every such file under BOOT back to the system and keeps the event log file to the system and administrators.
- Score
- CVSS 3.1 6.1
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- Affects
- Files and permissions
- Found
- in build 1282, by Claude (code review)
- Fixed
- in build 1301, 2026-11-20: update to build 1301 or later
- Published
- 2026-11-20
A crafted KFS disk could make Mizu read or write outside it
A KFS disk made to be malformed - one plugged in, for example - could get past two checks: one on the size of a range of blocks, and the checks on the volume's description after an unfinished change was completed at mount. Mizu could then read or write outside the volume on the same disk. Such a disk could also point a file, or the volume's own bookkeeping, at blocks holding the volume's metadata, so that writing a file damaged the volume itself. Block ranges are now checked so they cannot wrap around, and the volume's description is checked in full again after any unfinished change is completed; a disk that fails is not mounted. Since build 1213 every pointer on the disk is also checked against where KFS keeps its metadata, and the system never hands out or frees those blocks.
- Score
- CVSS 3.1 6.6
AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Affects
- File system (KFS)
- Found
- in build 1206, by Claude (code review)
- Fixed
- in build 1212, 2026-11-18: update to build 1212 or later
- Published
- 2026-11-18
A rename could overwrite a file's data
Renaming a file to a name inside another file, as if that file were a folder, was not refused on KFS: the other file's data was overwritten and the renamed file was lost. An account could do this only to files it may write. A rename into anything but a folder is now refused, and nothing changes.
- Score
- CVSS 3.1 3.3
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Affects
- File system (KFS)
- Found
- in build 1206, by Claude (code review)
- Fixed
- in build 1212, 2026-11-18: update to build 1212 or later
- Published
- 2026-11-18
A package could be taken back to an older signed version
mizupkg checked a package's description for the publisher's signature, but not that it was the version the current package list names. Every version ever published stays validly signed, so whoever could change what a machine downloads could have had it install an older version of a package, with the problems that version had. The system itself was not affected: it never goes back to an older build. A package is now installed only from the description of the version the signed package list names, fetched from that version's own place on the server; any other is refused, and nothing is changed. Each package also carries a signed number that only grows, and a package older than the one a system had is refused unless an administrator asks for it.
- Score
- CVSS 3.1 5.9
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- Affects
- Packages (mizupkg)
- Found
- in build 1198, by Claude (code review)
- Fixed
- in build 1200, 2026-11-18: update to build 1200 or later
- Published
- 2026-11-18
A program could cover the administrator's box and read what was typed into it
A program that took the whole screen while the administrator's box, the lock or the Ctrl+Alt+Del menu was up went over it, and received the keys typed for it, a PIN included; a program that took every screen level first could also keep those screens from appearing. The sign-in service's screens are now secure levels: a screen another program takes meanwhile goes under them, with no keys and no pointer, until the service is done; and the last screen level is kept for them.
- Score
- CVSS 3.1 6.0
AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
- Affects
- The screen (kernel graphics, sign-in service)
- Found
- in build 1143, by Claude (code review)
- Fixed
- in build 1147, 2026-11-16: update to build 1147 or later
- Published
- 2026-11-16
The local network could pose as a program on this machine
Since build 1139 connections to 127.0.0.1 stay inside the machine, but frames from the local network claiming to come from 127.0.0.1 were still taken, so a program that trusted a peer address of 127.0.0.1 on a listener open to all addresses could have been fooled. Frames from the network with a loopback source or this machine's own address as their source, or a loopback destination, are now dropped before they reach any connection or socket.
- Score
- CVSS 3.1 3.1
AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- Affects
- Network (kernel)
- Found
- in build 1139, by Claude (code review)
- Fixed
- in build 1142, 2026-11-16: update to build 1142 or later
- Published
- 2026-11-16
Kawa's Linux system could be changed by an account's programs without an administrator
Since build 1063 an administrator's yes runs Kawa's install and apk lines, but what they unpacked into Kawa's root belonged to the account that asked. Any program of that account, running without an administrator's rights, could rewrite the shell, apk or a package's scripts there, and the next line an administrator said yes to ran that code with an administrator's rights. What those lines make in Kawa's root now belongs to the system from the start and can be changed only by another line an administrator says yes to; roots made before are put right when the installer first starts. If you are concerned, reinstall Kawa's Linux system (kawa --install alpine).
- Score
- CVSS 3.1 7.3
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Affects
- Kawa (Linux programs)
- Found
- in build 1063, by Claude (code review)
- Fixed
- in build 1078, 2026-11-08: update to build 1078 or later
- Published
- 2026-11-08
A program ending during a disk command could garble the next one
When a program ended while one of its threads waited for a disk or USB command, the thread was dropped and its hold on the disk freed at once, with the command still under way. The next program to use the disk, another account's included, could then send its own command into the same slot, so wrong data could be written to or read from the disk, and a file system change was left half done. Ending a program at the right moment (Ctrl+C on a copy is enough) was all it took. Ending a program now waits for a disk or USB command of its own to finish, at most a minute, past every driver's own time limit and reset; nothing else of it runs meanwhile, and the next program finds the disk free.
- Score
- CVSS 3.1 5.8
AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
- Affects
- Disk access (kernel)
- Found
- in build 56, by Claude (code review)
- Fixed
- in build 1064, 2026-11-08: update to build 1064 or later
- Published
- 2026-11-08
A closed folder did not hide the files in it
Only a file's own rights, and its folder's when making or removing, were checked; the folders above it never were. So a file whose own rights let everybody read it, as Linux programs under Kawa often leave them, could be read by another account by its full path even inside a home only its owner may enter. Every folder on the way to a file must now let the account pass, as on Linux, for opening, looking up, listing, moving into and running from it; a file already open keeps working.
- Score
- CVSS 3.1 5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Affects
- File rights (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 1052, 2026-11-08: update to build 1052 or later
- Published
- 2026-11-08
A program in the background could follow and move the pointer
Any program could read where the pointer was and which buttons were pressed, whoever had the screen, and could move it: so a program in the background could follow where an account clicked, or put the pointer under a click meant for something else. Nothing in Mizu is typed with the pointer (no on-screen keyboard or PIN pad: PINs and passwords are typed with keys, which have been the screen's only since build 956). The pointer is now read and moved only by the program on the screen, the one it gives the keyboard to, or anybody when no screen is taken, as keys are.
- Score
- CVSS 3.1 4.4
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Affects
- The pointer (kernel input)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 1048, 2026-11-08: update to build 1048 or later
- Published
- 2026-11-08
The clock was set from the network without checking who answered
Since build 123, every hour the clock was set from a web server's time over plain HTTP, with no check of who answered and no limit on how far it moved. Someone on the network path could set the machine's clock to any date, which undoes certificate date checks (MZSA-2026-035) and can stop updates. The time now comes over HTTPS from two servers whose certificates are checked without relying on the clock; it must fall within every certificate's life and not before the system's build. Plain HTTP only corrects small drift, a few minutes in all; anything larger is offered in Date & time and set only after an administrator's yes.
- Score
- CVSS 3.1 6.5
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
- Affects
- The clock (the internet's time)
- Found
- in build 1043, by Claude (code review)
- Fixed
- in build 1046, 2026-11-08: update to build 1046 or later
- Published
- 2026-11-08
A program could use another program's graphics on a virtual machine
Only in a virtual machine with virtio-gpu (VIRTGPU.SYS): the graphics objects programs made had no owner, so any program could remove the desktop's, put its own over the whole screen (a false box or lock screen), or attach another program's to its own context and read its pixels back. Each graphics object and context is now its maker's: commands naming another program's are refused, only the system puts one on the screen, and a program's are freed when it ends.
- Score
- CVSS 3.1 6.6
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
- Affects
- Graphics in a virtual machine (virtio-gpu)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 1044, 2026-11-08: update to build 1044 or later
- Published
- 2026-11-08
A certificate made for something else was taken as a site's
A server's certificate was not checked for what it was made for: one issued for clients or for signing code, or one whose key may not sign, was taken as a site's, and an authority was taken whether or not its key could sign certificates, what it was for, or how many authorities it allowed below it. A site's certificate must now be one for servers whose key may sign, and each authority must be one that may sign certificates for servers, with no more authorities below it than it allows.
- Score
- CVSS 3.1 7.4
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Affects
- Secure connections (TLS)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 1042, 2026-11-08: update to build 1042 or later
- Published
- 2026-11-08
A forked program kept memory its parent gave back
A forked child kept the parent's graphics buffers, blocks and modules mapped, so when the parent freed them, or ended, the child could still write pages the kernel had handed out again. A forked child no longer has the parent's buffers, blocks or modules mapped; it gets its own memory, as on Linux.
- Score
- CVSS 3.1 8.8
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Affects
- Fork (kernel)
- Found
- in build 1025, by Claude (code review)
- Fixed
- in build 1026, 2026-11-07: update to build 1026 or later
- Published
- 2026-11-07
A file open on a FAT drive could be removed under its handle
On a FAT drive, removing, renaming or replacing a file that a program still had open gave its space back at once, so that program's later writes could land in another file, another account's included, since FAT keeps no rights. On a FAT drive, a file that is open is now busy: it cannot be removed, renamed or replaced until it is closed, as on Windows.
- Score
- CVSS 3.1 5.8
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L
- Affects
- FAT drives (kernel)
- Found
- in build 1021, by Claude (code review)
- Fixed
- in build 1022, 2026-11-07: update to build 1022 or later
- Published
- 2026-11-07
An installed driver was run whoever wrote it
A file named like a driver in \DRIVERS was run in the kernel without a look at who owned it or who could change it. An installed driver now runs only if it and its folder belong to the system and nobody else can change them.
- Score
- hardening (no known way to exploit), not scored
- Affects
- Drivers (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 1015, 2026-11-07: update to build 1015 or later
- Published
- 2026-11-07
A damaged partition table looked like an empty disk
A disk whose partition table was damaged or unreadable was shown to the installer as empty, so installing could write over what was on it. A damaged or unreadable table is now reported as such, never as an empty disk.
- Score
- CVSS 3.1 5.6
AV:P/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
- Affects
- Partitions (partition.c), the installer
- Found
- in build 927, by Koi Ayame
- Fixed
- in build 930, 2026-11-06: update to build 930 or later
- Published
- 2026-11-06
A GPT was used without checking it
A disk's GPT partition table was used without checking its checksums or keeping its entry list within the disk, so a crafted stick could make the kernel read where it should not. A GPT is now used only when its checksums hold, else its backup; its entries are read whole and within the disk.
- Score
- CVSS 3.1 5.2
AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
- Affects
- Partitions (partition.c)
- Found
- in build 927, by Koi Ayame
- Fixed
- in build 930, 2026-11-06: update to build 930 or later
- Published
- 2026-11-06
Paths were matched before they were made plain
The system image's place was matched on the path as given, so a path with ".." parts, through the kernel's own commands, could reach the folder under the image. Every path is now made plain before it is matched.
- Score
- CVSS 3.1 3.3
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Affects
- File system layer (vfs.c)
- Found
- in build 923, by Koi Ayame
- Fixed
- in build 927, 2026-11-05: update to build 927 or later
- Published
- 2026-11-06
A rename kept the replaced file's cached pages
Renaming over an existing file left the replaced file's pages in the cache, where they could have been served if its number was used again. A rename now forgets the replaced file's pages, as a removal does.
- Score
- CVSS 3.1 2.5
AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- Affects
- File system layer (vfs.c)
- Found
- in build 923, by Koi Ayame
- Fixed
- in build 927, 2026-11-05: update to build 927 or later
- Published
- 2026-11-06
A short disk read was kept as a file's end
When a disk read stopped part-way, the partial page was kept as the file's last page, so later reads came back cut short. A partial page is now kept only when it truly reaches the end of the file.
- Score
- CVSS 3.1 3.6
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
- Affects
- File system layer (vfs.c)
- Found
- in build 923, by Koi Ayame
- Fixed
- in build 927, 2026-11-05: update to build 927 or later
- Published
- 2026-11-06
A rights change could be read before it took effect
A file's rights, size or tags were changed outside the file system's lock, so another task could keep the old answer, and a right taken away could keep applying until the file was forgotten. These changes are now made under the lock, and the kept answers forgotten after them.
- Score
- CVSS 3.1 3.6
AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Affects
- File system layer (vfs.c)
- Found
- in build 923, by Koi Ayame
- Fixed
- in build 927, 2026-11-05: update to build 927 or later
- Published
- 2026-11-06
Files in shared folders could be removed by other accounts
In folders shared between accounts, any account could remove or replace another account's files, the App Store's pictures included. Shared folders are now sticky: only a file's owner, the folder's owner or the system removes or renames it; the App Store keeps each account's pictures in its own folder.
- Score
- CVSS 3.1 4.4
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- Affects
- Shared folders (kernel, desktop)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 1007, 2026-11-06: update to build 1007 or later
- Published
- 2026-11-06
Sound could keep playing freed memory
Freeing memory that a sound was still playing from did not stop the sound, so it kept reading memory given out again. Freeing memory now stops the sounds that play from it first.
- Score
- CVSS 3.1 3.8
AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
- Affects
- Sound (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 997, 2026-11-06: update to build 997 or later
- Published
- 2026-11-06
A program could unload another program's module
Loaded modules had no owner, so one program could unload another's, and unloading left the module's memory reachable. A module can now be unloaded only by the program that loaded it, and it is removed before its memory is freed.
- Score
- CVSS 3.1 8.8
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Affects
- Modules (kernel)
- Found
- in build 989, by Claude (code review)
- Fixed
- in build 991, 2026-11-06: update to build 991 or later
- Published
- 2026-11-06
Freed graphics memory stayed mapped
Memory of a freed drawing surface stayed reachable by the program after the kernel had given it out again. A surface is now removed from the program before its memory is freed.
- Score
- CVSS 3.1 8.8
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Affects
- Graphics (kernel)
- Found
- in build 988, by Claude (code review)
- Fixed
- in build 989, 2026-11-06: update to build 989 or later
- Published
- 2026-11-06
Programs could write lines that looked like the system's
Any program could write text into the system log that read like the kernel's or the sign-in service's own lines. Lines from programs that are not part of the system now carry the program's name.
- Score
- CVSS 3.1 2.8
AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
- Affects
- Kernel log
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 985, 2026-11-06: update to build 985 or later
- Published
- 2026-11-06
The random number pool had no lock of its own
Two callers at once could, on some machines, get the same random bytes. The pool is now changed under a lock of its own.
- Score
- hardening (no known way to exploit), not scored
- Affects
- Random numbers (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 984, 2026-11-06: update to build 984 or later
- Published
- 2026-11-06
A device list's count was not capped
The list of devices relied on a limit that was checked in one place but not where the list was filled. The count is now capped where the list is filled too.
- Score
- hardening (no known way to exploit), not scored
- Affects
- Devices (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 981, 2026-11-06: update to build 981 or later
- Published
- 2026-11-06
A program could change other programs' sounds
Any program could stop or change another program's sounds and the master volume. A program now touches only its own sounds; the master volume is the system's.
- Score
- CVSS 3.1 3.3
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- Affects
- Sound (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 980, 2026-11-06: update to build 980 or later
- Published
- 2026-11-06
A permissions change could be lost after a crash
A change to a file's rights made shortly before an unclean stop could come back undone at the next start. Changes to rights and attributes are now written to disk at once.
- Score
- CVSS 3.1 3.3
AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
- Affects
- File system (KFS)
- Found
- in build 977, by Claude (code review)
- Fixed
- in build 978, 2026-11-06: update to build 978 or later
- Published
- 2026-11-06
An elevated program's terminal could be joined
A terminal made by a program running with an administrator's rights could be read and typed into by the same account's ordinary programs. Such a terminal is now kept from programs without those rights.
- Score
- CVSS 3.1 6.6
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
- Affects
- Terminals (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 977, 2026-11-06: update to build 977 or later
- Published
- 2026-11-06
A signature's length was not checked against its message
A server's signature length was taken from the message without checking it fit, so the checker could read past the message. The length is now checked against the message.
- Score
- CVSS 3.1 4.3
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
- Affects
- Secure connections (TLS 1.3)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 976, 2026-11-06: update to build 976 or later
- Published
- 2026-11-06
A TLS 1.3 server without a certificate was accepted
A secure connection could open to a server that proved nothing about who it was. The kernel refuses such a connection, and media streams play only from servers whose identity was checked.
- Score
- CVSS 3.1 4.2
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
- Affects
- Secure connections (TLS 1.3), media streams
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 974, 2026-11-06: update to build 974 or later
- Published
- 2026-11-06
Any program could stop any other
A program could send a stopping signal to programs of other accounts and of the system. A program can now signal only programs of its own account; the system can signal any.
- Score
- CVSS 3.1 5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Affects
- Signals (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 972, 2026-11-06: update to build 972 or later
- Published
- 2026-11-06
A certificate's length could overflow
A length in a certificate could make the reader's bounds check overflow, crashing the reader on a crafted certificate from any server. Lengths are now checked without overflow.
- Score
- CVSS 3.1 6.5
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Affects
- Certificates (x509)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 971, 2026-11-06: update to build 971 or later
- Published
- 2026-11-06
A drawing request's size could overflow
A screen area's position plus its width was computed in a type that could overflow, so a request could reach outside the screen's memory. These sums are now done in 64 bits and checked.
- Score
- CVSS 3.1 8.8
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Affects
- Graphics (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 970, 2026-11-06: update to build 970 or later
- Published
- 2026-11-06
A signal could be written into freed memory
A program's signal word was not checked again after the memory holding it had been freed. The kernel checks the memory is still the program's before writing.
- Score
- CVSS 3.1 8.8
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Affects
- Signals (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 968, 2026-11-06: update to build 968 or later
- Published
- 2026-11-06
One clipboard for every account
Any program of any account could read the clipboard, so text one account copied could be read by another's programs. The clipboard now belongs to the account that copied; it is emptied when a session ends.
- Score
- CVSS 3.1 4.4
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Affects
- Clipboard (kernel, sign-in service)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 967, 2026-11-06: update to build 967 or later
- Published
- 2026-11-06
A permissions request was read twice
When changing a file's owner or rights, the request was checked and then read again, so it could be changed in between. The kernel copies the request once and uses that copy.
- Score
- CVSS 3.1 4.7
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
- Affects
- File permissions (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 967, 2026-11-06: update to build 967 or later
- Published
- 2026-11-06
Closing a file during a read could mix up files
A file closed by one thread while another was still reading from it could let the read return another file's data. Closing a file now waits for calls still working on it.
- Score
- CVSS 3.1 6.3
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
- Affects
- Files (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 963, 2026-11-06: update to build 963 or later
- Published
- 2026-11-06
Ctrl+Alt+Del could be held back by a full-screen program
A program covering the whole screen received Ctrl+Alt+Del itself, so it could hide the real lock screen behind one of its own. Only real Ctrl+Alt+Del presses count, and only the sign-in service hears them; its menu always comes over the screen.
- Score
- CVSS 3.1 5.0
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
- Affects
- Ctrl+Alt+Del (kernel, sign-in service)
- Found
- in build 955, by Claude (code review)
- Fixed
- in build 962, 2026-11-06: update to build 962 or later
- Published
- 2026-11-06
Machine-wide system calls did not check the caller's rights
Several system calls that change the machine (raw disk reads, the clock, the network, drivers) accepted any program of the system image without looking at its account. The system's calls that act on the machine now check who asks: the system, an administrator, or the program holding the screen, as fits each; the desktop asks the sign-in service for what it needs.
- Score
- CVSS 3.1 7.3
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Affects
- System calls that act on the machine (kernel)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 960, 2026-11-06: update to build 960 or later
- Published
- 2026-11-06
Any program could read what was typed
The keyboard had no owner, so a program left running in the background could read keys typed elsewhere, passwords included. Keys now go only to the program on the screen and to the one window it hands the keyboard to.
- Score
- CVSS 3.1 5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Affects
- Keyboard (kernel), desktop
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 956, 2026-11-06: update to build 956 or later
- Published
- 2026-11-06
A program could answer the administrator's box
Keys and clicks sent by a program looked the same as real ones, so code running in an administrator's own session could say yes to its own request. The kernel marks input a program sent; the box asks for the administrator's password or PIN whenever its answer did not come from a person at the computer.
- Score
- CVSS 3.1 7.3
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Affects
- Input and the administrator's box (kernel input, sign-in service)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 954, 2026-11-06: update to build 954 or later
- Published
- 2026-11-06
Pipe files were shared by every account
A pipe's temporary file was made in one place for every account, so another account could read or change what flowed through it. Pipe files are now made in each account's own temporary folder, readable only by it.
- Score
- CVSS 3.1 3.3
AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
- Affects
- Command shell pipes (command.c)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 951, 2026-11-06: update to build 951 or later
- Published
- 2026-11-06
Shell built-ins wrote files without checking rights
Some of the command shell's built-in commands that write files did not check the caller's rights, so a standard account could change files it should not. Built-ins now write files with the caller's own rights.
- Score
- CVSS 3.1 7.8
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Affects
- Command shell built-ins (command.c)
- Found
- in build 947, by Claude (code review)
- Fixed
- in build 950, 2026-11-06: update to build 950 or later
- Published
- 2026-11-06