Read next

Mecare – Hospital and Health PHP Template Free Download. Mecare is a Premium, High-performance PHP Template engineered Specifically for Hospitals, Medical Clinics, Healthcare Centers, Specialized Doctors, and Dental Practices. Featuring a Clean, Highly Professional, and Trust-inspiring Aesthetic, Mecare provides the Ultimate Digital Infrastructure for Healthcare Facilities to Showcase Medical Departments, and Highlight Doctor Profiles.

Main Features

• 3+ Homepages
• Responsive Design
• Built alongside HTML5 and CSS3
• 360+ Icons
• Easy to Customize
• Sticky Header
• Based on Bootstrap
• Google Fonts
• Wow Animations
• Retina Ready
• and more

Download Mecare – Hospital and Health PHP Template

Free download Mecare – Healthcare and Dental PHP Template by zcubethemes on Themeforest 64247486 premium healthcare medicinal and dentists HTML theme download.

Read next

Apa Sebenarnya Peran Seorang Data Scientist?

Channel ini menyajikan materi seputar Data Science & Artificial Intelligence, Networking & Cyber Security, serta Database & Programming. Seluruh materi disusun secara sistematis untuk membantu Anda memahami konsep, teknologi, dan praktik yang digunakan di bumi teknologi informasi, mulai dari tingkat alas hingga lanjutan. Setiap bahasan berfokus pada pengembangan keahlian melalui materi yang gampang dipahami, relevan dengan kebutuhan industri, dan disampaikan untuk tujuan edukasi. Seluruh konten mengedepankan implementasi teknologi secara legal, etis, dan bertanggung jawab, sehingga dapat menjadi rujukan belajar bagi pelajar, mahasiswa, maupun profesional. Jika Anda mau mengembangkan kapasitas di sektor pemrograman, pengelolaan data, kecerdasan buatan, jaringan komputer, maupun keamanan siber, channel ini menyediakan materi yang dapat membantu membangun fondasi ilmu sekaligus menaikkan keahlian secara bertahap. Playlist video terkait: ▪ https://www.youtube.com/playlist?list=PLZGgeqmsm32s ▪ https://www.youtube.com/playlist?list=PLZomBNpDl3vc ▪ https://www.youtube.com/playlist?list=PLE5VyXMZkzb8 PEMBAHASAN MATERI Playlist Materi Ilmu Komputer berisi kumpulan video pembelajaran, tutorial, klarifikasi konsep, studi kasus, demo, dan bahasan komplit seputar beragam sektor dalam ilmu komputer. Materi yang disajikan mencakup alas hingga tingkat lanjut, mulai dari pemrograman, pengelolaan database, jaringan komputer, keamanan siber, mekanisme operasi, pengembangan alat lunak, arsitektur komputer, hingga beragam teknologi yang digunakan dalam bumi komputasi modern. Temukan bahasan mengenai komputer dan pemrograman, algoritma, struktur data, PHP, JavaScript, Python, Laravel, MySQL, PostgreSQL, API, rekayasa alat lunak, database, jaringan komputer, pengelolaan server, cloud computing, virtualisasi, Linux, Windows Server, keamanan jaringan, cyber security, ethical hacking, kriptografi, keamanan aplikasi, DevOps, Internet of Things (IoT), kecerdasan buatan (AI), machine learning, serta beragam konsep, teknologi, dan praktik terbaik di sektor ilmu komputer. Playlist ini cocok bagi pelajar, mahasiswa, programmer, web developer, software engineer, pengelola sistem, ahli IT, maupun siapa saja yang mau mempelajari dan memperdalam wawasan di bumi ilmu komputer secara menyeluruh. CONTACT US ▪ Email support@mycoding.id ▪ WhatsApp https://wa.me/6281274309663 ▪ Telegram https://t.me/mycodingxd OFFICIAL LINKS ▪ Web https://mycoding.id ▪ Blog https://blog.mycoding.id ▪ News https://en.mycoding.id ▪ Apps https://play.google.com/store/apps/dev?id=5237501547073493079 SOCIAL MEDIA ▪ https://linkedin.com/company/mycodingxd ▪ https://facebook.com/mycodingxd ▪ https://instagram.com/mycodingxd ▪ https://tiktok.com/@mycodingxd ▪ https://twitter.com/mycoding_xd ▪ https://pinterest.com/mycoding_xd CHANNEL LINKS ▪ YouTube https://safelink.asia/youtube ▪ DailyMotion https://safelink.asia/dailymotion ▪ WhatsApp https://safelink.asia/whatsapp ▪ Telegram https://safelink.asia/telegram Powered by https://linkedin.com/company/401XDGroup #CyberSecurity #ArtificialIntelligence #Networking #DataScience #Programming #Database

Read next

Active eCommerce Flutter App v5.8.0 – Source Code Free Download. This Flutter app is Available lone for Active eCommerce CMS. If you do not acquisition Active eCommerce CMS yet afterward click current for Purchasing.

Main Features

• Dynamic Slider Section
• Top Categories
• Top Categories and Featured Categories
• Android and iOS
• Advanced Product Search
• Advance Product Sorting Option
• Smart Image Gallery
• Related Product Presentation
• Seller Chatting
• Customer Login and Registration
• Social Login
• Wishlist and Wallet History
• Customer Profile
• Top Selling Products
• and more

Download Active eCommerce Flutter App Source

v5.8.0

v5.6.0

v5.5.0

v5.4.0

v5.3.0

v4.9.0

v4.8.0

Free download Active eCommerce Flutter App origin code by ActiveITzone on Codecanyon 31466365 premium eCommerce mobile use for Active eCommerce.

Read next

CVE-2026-98432 is a use-after-free in the Linux kernel’s IPv4 TCP handshake path. The flaw appears whenever two processors act on connected petition and kid sockets during the two can motionless citation the identical IP options object. One way may liberated that entity immediately during another path, protected lone as an RCU reader, continues to use it. The outcome is a old kernel pointer in code reachable through network traffic.

The concise clarification appears akin a acquainted kernel race, but the community evidence demands careful interpretation. The CVE record carries a CVSS 3.1 mark of 9.8, representing a network-reachable, unauthenticated worst case alongside elevated confidentiality, integrity, and preparedness impact. Red Hat’s merchandise analysis assigns a lesser 5.9 mark since it treats exploitation as a difficult competition and assesses the applicable consequence in its supported products additional conservatively. Separately, Anthropic’s Frontier Red Team reported a operating distant base code-execution sequence against a Linux server alongside a Multipath TCP listener in a controlled lab. That outcome is grave evidence of exploitability under a particular configuration. It is not evidence that all unpatched Linux server, all average TCP listener, or all allocation build can be compromised in the identical way.

Defenders should treat those statements as complementary. The upstream document identifies a hazardous memory-lifetime error and its theoretical maximum impact. A allocation mark describes the vendor’s shipped code, configuration, mitigations, and expected utilize conditions. A investigation utilize demonstrates one tangible way through a particular target. None of the three have to be discarded, and none have to be stretched beyond its scope.

The applicable reply is direct: acknowledge reachable Linux TCP services, decide which vendor kernel is really running, instal the vendor-provided fixed build, reboot into it, and keep evidence that the operating kernel contains the correction. Hosts that disclose MPTCP listeners deserve contiguous notice since the community investigation specifically validated that environment. Internet-facing gateways, burden balancers, Kubernetes nodes, VPN endpoints, reverse proxies, and appliances that use Linux networking additionally deserve a accelerated inventory equal if they do not intentionally allow MPTCP.

What is confirmed concerning CVE-2026-98432

The authoritative specialized clarification comes from the Linux kernel CVE procedure and the upstream patch. The matter involves ownership and reclamation of IPv4 choice data connected alongside a TCP petition socket. During the server flank of a TCP handshake, the kernel creates a lightweight petition socket to portray a association that has not yet rotate into a complete kid socket. When the handshake progresses, tcp_v4_syn_recv_sock() transfers the request’s ireq_opt pointer to the new kid socket as inet_opt. It does not copy the object.

At the identical time, a distinct CPU can procedure a retransmitted SYN connected alongside the identical request. That second way can dispatch another SYN-ACK through tcp_check_req(). Functions specified as tcp_v4_send_synack() and inet_csk_route_req() peruse the request’s IP options inner an RCU read-side crucial section. Later helpers, including ip_build_and_send_pkt() and ip_options_build(), dereference sectors from the options object. The Debian safety tracker reproduces the upstream clarification and maps the matter to fixed Debian kernel packages.

The life mismatch is the center problem. The audience behaves as although RCU protects the object, but the destructor frees it alongside average kfree(). Ordinary kfree() makes the allocation accessible for reuse without waiting for existing RCU readers to finish. If the kid socket is destroyed during a retransmitted-SYN way motionless uses the options, the second CPU can continue study recollection that no longer belongs to that object. The chief upstream fix replaces contiguous freeing alongside kfree_rcu() in the applicable destructors, delaying reclamation until an RCU grace duration has elapsed.

The exposure additionally has a connected request-migration case. If net.ipv4.tcp_migrate_req=1 is enabled, or if a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program controls petition migration, the kernel may copy a petition socket. The old petition and its copy can temporarily portion the identical options object. A CPU holding a citation to the old petition can motionless use the entity during the copy is freed. The kernel clarification hence changes the two inet_sock_destruct() and tcp_v4_reqsk_destructor() to use RCU-aware reclamation.

The archetypal matter is particular to the IPv4 child-socket way since the corresponding IPv6 function duplicates options alternatively of transferring the identical pointer. The upstream content additionally notes an IPv6 request-migration involvement involving ipv6_opt whenever CALIPSO is current and says that circumstance is handled separately. That difference matters: a declaration that “IPv6 is unaffected” is too broad, during a declaration that the chief IPv4 ownership-transfer bug does not use to the average IPv6 kid innovation way is accurate.

The place was merged upstream as commit e3f33b0a1d89, titled “ipv4: liberated inet_opt and ireq_opt following an RCU grace period.” The Ubuntu CVE page identifies the identical introduction and fix commits and tracks many Ubuntu kernel flavors independently. This is helpful evidence that a generic kernel type inspect cannot substitute distribution-specific status.

Facts that are not established

No authoritative origin cited current establishes general exploitation throughout the community internet. Anthropic established that its researchers could rotate the flaw into distant base command implementation against a controlled mark alongside an MPTCP listener. That is stronger than a crash-only evidence and should power urgency. It motionless does not provision a measured prevalence of susceptible MPTCP services, a worldwide achievement rate, or evidence that the identical utilize sequence plant unchanged throughout kernel builds, CPU architectures, allocators, hardening profiles, and network paths.

The community matter additionally does not validate assuming that any elevated quantity of SYN retransmissions is exploitation. Retransmitted SYN packets happen naturally since of packet loss, asymmetric routing, overloaded services, client retry behavior, and middleboxes. Exploitation of a competition may create different patterns, but those patterns need association alongside a susceptible host, applicable options, kernel symptoms, and timing. A network vigilant can prioritize investigation; it cannot demonstrate a use-after-free occurred inner the kernel.

There is no sole upstream type cord that accurately labels all vendor kernel. Enterprise distributions routinely backport safety fixes during retaining an older-looking basis version. Cloud providers and appliance vendors may container their own kernel builds. A scanner that compares lone uname -r against an upstream publish catalog can create the two false positives and false negatives. The defensible decision comes from a vendor advisory, bundle changelog, build metadata, VEX statement, or straightforward confirmation that the applicable fix commit was backported.

Finally, disabling MPTCP does not eliminate the underlying IPv4 life bug. It removes the exact listener configuration used in the community investigation sequence and can meaningfully decrease contiguous visibility anywhere MPTCP is unnecessary. The upstream specialized clarification covers the average IPv4 TCP petition and kid socket paths as fine as petition migration. Patch deployment remains the durable correction.

How the susceptible TCP way works

A TCP server normally receives a SYN, replies alongside SYN-ACK, and waits for the final ACK. The kernel avoids allocating a complete connected socket at the archetypal packet since an attacker could alternatively exhaust resources cheaply. Instead, it creates a compact petition socket that stores adequate province to validate and complete the handshake. When the ACK arrives and the association is accepted, the kernel creates a complete kid socket and moves or copies selected province into it.

IPv4 options complicate that transition. IP options can transport metadata that influences routing or packet processing. The kernel parses the incoming data and stores an inner depiction for afterward reply construction. In the affected path, the petition socket’s ireq_opt pointer becomes the kid socket’s inet_opt pointer. The transfer avoids a copy, but it method the life of one allocation crosses the border between two socket objects.

A second SYN for the identical association tuple can attain before the handshake province has entirely settled. Retransmission is a normal part of TCP. The kernel may procedure that SYN on another CPU and build a SYN-ACK using the first petition socket. Since Linux networking is extremely parallel, the kid socket can advancement toward teardown during the another CPU is motionless constructing the reply. The petition way takes an RCU peruse lock, indicating that the data it says must remain valid until the read-side crucial division ends.

The old destructor behavior violated that expectation. The kid socket did not transport the SOCK_RCU_FREE behavior that would defer its complete release, and inet_sock_destruct() freed inet_opt directly. The second CPU could keep the pointer and peruse optlen from recollection that had already returned to the allocator. A afterward allocation could location unrelated data at that address, changing the value between says or letting consequent code run on attacker-influenced contents.

Use-after-free bugs are hazardous since the contiguous indication depends on what replaces the freed allocation. The old admission may peruse the old bytes and appear harmless. It may encounter poisoned or unmapped recollection and crash. It may peruse a new kernel entity and disclose data. With adequate authority complete allocation patterns and timing, a investigator may rotate the old citation into a additional mighty read, write, or control-flow primitive. The exposure category hence supports outcomes ranging from intermittent handshake nonaccomplishment through denial of assistance to code execution, but a particular outcome must be demonstrated for a particular target.

The request-migration type follows the identical life regulation through a distinct topology. Reuseport allows multiple sockets to portion a listening port, and BPF can act in choosing a target. Request immigration may move pending connections whenever a listener changes state. The kernel clones petition state, creating a opening in which two petition objects mention to the identical options allocation. Clearing the pointer in one entity does not defend a CPU that already holds a citation to it. If the another object’s destructor immediately frees the shared allocation, that audience becomes stale.

The place does not attempt to serialize all procedure rearward one earth lock. That would damage scalability in a hot network path. It alternatively aligns reclamation alongside the synchronization example that readers already use. This is exactly the benevolent of issue Read-Copy Update is designed to solve.

Why RCU changes the safety boundary

Read-Copy Update lets readers admission shared data alongside extremely low overhead during writers publish replacements and defer freeing old versions. A audience enters an RCU read-side crucial section, obtains a pointer, uses the object, and exits. A author can eliminate the entity from the data construction so new readers no longer discover it, but it must delay for a grace duration before reclaiming memory. A grace duration ensures that all readers that could have seen the old pointer have finished.

The Linux kernel’s RCU documentation describes the essential removal-and-reclamation split. Removal changes reachability. Reclamation returns retention to the allocator. Conflating those operations is a average origin of use-after-free errors. An RCU fastener does not location a citation figure on an arbitrary entity and does not create straightforward kfree() safe. The corresponding author must use an RCU-aware scheme specified as call_rcu() or kfree_rcu().

In CVE-2026-98432, the peruse paths already use RCU. The correction makes the destructor regard that contract. kfree_rcu() schedules the entity for publish following a grace duration fairly than releasing it immediately. The CPU construction the SYN-ACK can complete study the old options object. Later readers volition no longer get it, and the allocation becomes reusable lone following the preexisting readers are gone.

This scheme preserves concurrency. It does not necessitate the server to halt handling retransmissions, location a ample fastener about handshake construction, or copy the options entity for all read. The safety asset is narrow and clear: an entity apparent to an RCU audience remains allocated for the duration in which that audience power admission it.

RCU fixes additionally explain why packet filtering solitary cannot be a complete remedy. The memory-safety defect is in entity life management. Filtering may create a trigger harder to reach, and disabling unneeded features can decrease the set of paths. Only corrected reclamation restores the invariant for all lawful and antagonistic packet that reaches the code.

Reconciling the 9.8 and 5.9 scores

The CVE record’s CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, producing 9.8. This vector assumes a network attacker needs no document and no person interaction, that assault complexity is low, and that prosperous exploitation can have elevated effect throughout confidentiality, integrity, and availability. It expresses the CNA’s basis characterization of the susceptible upstream component.

Ubuntu displays that 9.8 value but additionally publishes a CVSS 4.0 appraisal of 8.3 alongside assault requirements present. CVSS 4.0 can portray prerequisites that do not fit cleanly into the older vector. Ubuntu’s leaf labels the exposure elevated precedence and exposes package-by-package states fairly than treating the numeric mark as the complete decision.

Red Hat’s 5.9 mark reflects a distinct assessment. Red Hat evaluates vulnerabilities in the environment of its products, backports, default configurations, mitigations, and apt consequences. Its inspection treats the competition as elevated complexity and emphasizes that a dependable safety effect may be a collision or denial of service, during recollection misconduct and stronger outcomes depend on additional conditions. A lesser vendor mark does not average the upstream bug is imaginary; it method the vendor does not obtain all worst-case metric for the products it ships.

CVSS disagreement is average for open-source components distributed in distinct forms. The identical origin defect may be current in two products but exposed through distinct configurations. One vendor may allow a characteristic by default, another may omit it, and a third may transport a partial backport that changes reachability. Kernel hardening, allocator behavior, architecture, compiler options, and assistance topology can all power utilize betterment without changing the susceptible origin line.

For operational prioritization, a sole worldwide mark is small helpful than a abbreviated environment-specific analysis:

The 9.8 mark is helpful for recognizing the possible ceiling. The 5.9 mark is helpful for understanding Red Hat’s product-specific view. Neither figure should override the fact that an exposed MPTCP mark was exploited in a lab, and the lab outcome should not be converted into a assertion of bulk exploitation. Defenders can act urgently during preserving those distinctions.

What the Anthropic MPTCP investigation proves

Anthropic’s October 27 investigation post describes a remote, zero-click Linux kernel utilize against a server alongside a Multipath TCP listener. According to the researchers, the utilize used the race-induced use-after-free in two stages. The archetypal phase obtained a kernel pointer and defeated Kernel Address Space Layout Randomization. The second phase converted the recollection misconduct into control-flow hijacking and ultimately ran an attacker-chosen command as root.

The squad reports that its evidence of idea took about 48 minutes to disclose a kernel pointer and another five minutes to attain command execution. A unsuccessful attempt could depart the handshake incomplete without necessarily crashing the host, allowing repeated trials. That behavior is applicable since race-condition exploits frequently rotate into applicable whenever nonaccomplishment is cheap and retries are plentiful.

The investigation is dependable evidence that the exposure can exceed denial of service. It additionally tells defenders which community visibility deserves the highest priority: untrusted network admission to an MPTCP-enabled listener on a susceptible kernel. The authoritative Linux MPTCP documentation explains how Multipath TCP extends average TCP so a association can use multiple subflows during remaining compatible alongside existing applications. Linux distributions may provision MPTCP assistance without all use or assistance using it, so administrators need to inspect runtime province and listeners fairly than infer visibility from bundle presence.

The published summary is not a reusable utilize recipe. It omits the target-specific particulars required to reproduce heap state, timing, location disclosure, and dependable control. Responsible defence does not necessitate reproducing those stages on manufacturing systems. The beingness of a operating investigation chain, coordinated disclosure, upstream correction, and stable backports supplies adequate evidence to patch.

Several boundaries should remain explicit. The investigation mark used MPTCP. Kernel builds differ. The reported period is one experimental result, not a guaranteed minimum or maximum. Network latency, CPU count, load, allocator behavior, hardening, and assistance implementation can alter the race. The article does not say that an average TCP assistance alongside default settings on all allocation is equivalently exploitable.

The most defensible wording is therefore: CVE-2026-98432 is remotely reachable through Linux networking; Anthropic demonstrated unauthenticated base code implementation against a susceptible MPTCP listener in a controlled environment; broader exploitability and reliability depend on the target. This declaration preserves the two urgency and accuracy.

Affected versions and vendor backports

The susceptible behavior was introduced by older upstream changes, including commit 079096f103fa, which allowed TCP and DCCP petition sockets to be installed in the established hash array without the listener lock, and another alter connected alongside petition migration. Because the affected former spans many maintained branches, the Linux CVE document enumerates branch-specific fixes fairly than one uncomplicated susceptible range.

Upstream stable fixes were issued throughout maintained lines. The archetypal corrected releases identified in the community document contain 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, and the 7.3 betterment row containing the mainline fix. These numbers are helpful for upstream kernels. They must not be used as a worldwide regulation for vendor packages since vendors may backport the correction to builds alongside lesser basis numbers or keep a branch alongside additional revision identifiers.

Debian’s tracker, for example, marks Bookworm’s 6.1.190-1 safety bundle and Trixie’s 6.12.113-1 bundle fixed. It additionally records fixed builds in afterward suites. Those bundle versions are the accurate evidence for Debian systems. On Ubuntu, the safety leaf lists many distinct kernel origin packages, including generic, AWS, Azure, GCP, KVM, Oracle, OEM, low-latency, and real-time variants. A position for one sensation does not automatically demonstrate another sensation is fixed.

Red Hat customers should use the Red Hat CVE leaf and errata applicable to the exact RHEL or OpenShift product. Enterprise kernels deliberately keep stable interfaces and type families during incorporating safety patches. A version-only scanner that expects the upstream first-fixed type may emblem a corrected Red Hat kernel. Conversely, seeing a elevated basis type in an appliance does not demonstrate the vendor included all stable patch.

The SUSE CVE page, Gentoo safety advisories, cloud-provider notices, and appliance vendor bulletins have to be consulted for their corresponding products. When a vendor has not published a determination, administrators can ask for a VEX or assistance declaration identifying whether the susceptible code is current and which build includes the fix.

Containers deserve particular attention. Containers normally portion the presenter kernel. Updating an use depiction does not substitute the kernel that handles its TCP traffic. Managed Kubernetes customers may need a node-image update, a node-pool rollout, or a provider care action. Self-managed clusters need presenter bundle updates and node reboots. After replacement, verify all node fairly than assume the authority aircraft rollout reached the complete fleet.

Live patching may or may not shield this change. The correction affects entity reclamation in network destructors, and safety depends on the vendor’s live-patch implementation and assistance decision. Treat a live-patch position as valid lone whenever the vendor explicitly associates it alongside CVE-2026-98432. If no specified confirmation exists, instal the fixed kernel and reboot.

Build an visibility inventory before the alter window

A fine inventory separates exposure existence from assault reachability. Presence asks whether the operating kernel contains the affected code without the correction. Reachability asks which untrusted networks and services can exercise the applicable handshake paths. Both matter. A susceptible but secluded lab presenter can prosecute a planned update window, during a community MPTCP assistance should move to the forefront of the queue.

Start alongside systems that terminate TCP immediately on Linux: reverse proxies, web servers, API gateways, ingress nodes, VPN concentrators, burden balancers, communication gateways, DNS-over-TCP services, SSH bastions, repository endpoints, and tradition daemons. Include appliances if their vendor identifies Linux internally. A hardware-looking border merchandise can motionless disclose a Linux network stack.

Determine whether a distinct equipment terminates the external connection. A haze burden balancer may assimilate the community handshake and established a second association to a backend. That can decrease straightforward reachability of the backend kernel from the internet, but the burden balancer itself and any inner untrusted clients remain in scope. Preserve the genuine association way in the asset document alternatively of relying on use architecture diagrams that omit network termination.

Check MPTCP status. On systems alongside an suitable iproute2 version, ip mptcp endpoint display and ip mptcp limits display can display configured endpoints and limits. Inspect sysctl net.mptcp.enabled anywhere available. Also acknowledge applications that deliberately create MPTCP sockets; a earth allow emblem solitary does not demonstrate a listener exists. The MPTCP upstream project documentation provides evaluation and deployment references.

Inspect request-migration settings alongside sysctl net.ipv4.tcp_migrate_req. The default and preparedness can change alongside kernel and configuration. A value of one increases relevance of the immigration way described upstream. Identify reuseport BPF programs attached to listening groups. The kernel’s SK_REUSEPORT BPF documentation explains the program category and socket choice context. Absence of these features does not demonstrate the chief IPv4 way is safe, but existence helps prioritize evaluation and rollout.

Record the productive kernel, package, booted image, architecture, and vendor. For immutable systems, document the node depiction or operating-system release. For appliances, document the firmware. For managed services, grasp the provider advisory or assistance case. This evidence is additional helpful than a spreadsheet division that lone says “Linux.”

Map rely boundaries. A assistance reachable lone from a company VLAN may motionless be reachable by compromised laptops, workloads, or partners. Kubernetes node ports can disclose listeners in ways that differ from ingress configuration. IPv4 visibility remains applicable equal in organizations that favor IPv6, since dual-stack services and administration networks frequently keep IPv4 enabled.

Safe validation without utilize traffic

Production validation should answer four questions: what kernel is running, what vendor bundle supplied it, whether applicable services are reachable, and whether the vendor says that exact build is fixed. It should not attempt to win the race, corrupt kernel memory, disclose addresses, or run commands through a evidence of concept.

The following commands collect local facts on a scheme you administer. They do not trigger the vulnerability:

uname -a uname -r cat /etc/os-release # Debian and Ubuntu bundle evidence dpkg-query -W 'linux-image*' 2>/dev/null | sed -n '1,40p' # RHEL-family bundle evidence rpm -q kernel kernel-core 2>/dev/null # Listening TCP sockets ss -lntp # MPTCP province whenever supported sysctl net.mptcp.enabled 2>/dev/null ip mptcp endpoint display 2>/dev/null ip mptcp limits display 2>/dev/null # Request immigration environment whenever present sysctl net.ipv4.tcp_migrate_req 2>/dev/null 

Run commands alongside the smallest privilege needed. Process names in ss output may necessitate elevated permission, but listener addresses and ports are motionless helpful without them. Do not paste complete command output into a community ticket if it contains hostnames, inner addresses, or assistance details.

Next, difference the installed bundle alongside the distribution’s advisory. On Debian, use the Debian tracker and the installed source-package version. On Ubuntu, choose the exact kernel sensation and publish row. On Red Hat, use the applicable merchandise province and erratum. If the vendor says a build is fixed through a backport, obtain that mapping complete a generic upstream comparison.

Confirm that the scheme booted the updated kernel. Package facility can win during the operating kernel remains old. Compare uname -r alongside the expected installed depiction following reboot. On systems alongside multiple footwear entries, verify the bootloader selected the accurate image. In a cluster, collect the outcome from all node.

For externally reachable services, validate visibility from an authorized appraisal presenter using average association attempts, load-balancer configuration, firewall policy, and assistance discovery. There is no need to transmit malformed IP options or repeated race-triggering handshakes. Standard TCP connectivity is adequate to established that untrusted traffic reaches the host.

If a lab squad needs deeper assurance, build a available surroundings using the identical vendor image, allow kernel sanitizers lone in that environment, and run vendor-approved regression tests. KASAN documentation describes the kernel’s memory-error detector. KASAN is precious for betterment and confirmation, but its achievement disbursal and altered recollection layout create it unsuitable as a manufacturing mitigation and can alter utilize timing.

A harmless validation study should merge the asset identifier, endeavor service, network exposure, MPTCP state, request-migration province if relevant, bundle version, operating kernel, vendor advisory URL, update timestamp, reboot evidence, service-health result, and any impermanent exception. That document supports event response, audit, and afterward rescanning.

Detection and event response

Memory-corruption exploitation rarely produces one conclusive log line. Detection should merge kernel telemetry, network behavior, presenter state, and the known susceptible build. A kernel collision alongside a stack near ip_options_build(), ip_build_and_send_pkt(), TCP SYN-ACK construction, or socket demolition deserves contiguous review. KASAN reports that acknowledge a use-after-free involving inet_opt or ireq_opt are particularly applicable in test or debug environments.

Review journalctl -k, dmesg archives, collision dumps, and phase serial-console logs. Cloud instances may reboot before local logs are flushed, so centralized kernel logs and provider console former matter. If kdump is deployed, maintain the vmcore, matching unstripped kernel symbols, bundle metadata, and footwear configuration. Do not immediately recycle an affected node if evidence gathering is part of the event plan.

Network telemetry can acknowledge clients that dispatch repeated association attempts alongside different choice combinations or prolong retries against an MPTCP listener. Baseline first. Mobile networks, lossy links, health checks, and SYN proxies can create elevated retransmission counts. An vigilant should contain destination service, origin distribution, TCP choice summary, rate, duration, and whether the mark was susceptible at the time.

An utilize described by Anthropic needed repeated opportunities complete a lengthy interval. Long-lived patterns from a sole origin or coordinated sources may hence be additional engaging than a small burst. Attackers can allocate retries, and normal clients can additionally retry for extended periods. Treat the form as investigative environment fairly than a signature.

Endpoint finding agents have constricted visibility into an utilize that starts and executes inner the kernel. A prosperous control-flow hijack power afterward create a user-space procedure or alter credentials, but it may additionally execute actions that blend into normal privileged activity. Correlate unexpected base processes, changes to startup configuration, new network connections, component activity, audit events, and integrity-monitoring alerts alongside kernel and network evidence.

If exploitation is suspected, isolate the presenter through network controls that maintain evidence, grasp volatile province according to the organization’s event process, rotate credentials that the presenter could access, and examine neighboring systems. A kernel-level colony invalidates assumptions concerning user-space logs and delegate integrity. Rebuild from a trusted depiction following evidence gathering fairly than treating a bundle update as remediation for an already compromised machine.

Check whether the scheme exposed MPTCP and whether the doubtful origin could attain it. Preserve firewall, load-balancer, flow, packet-capture, and assistance configuration about the event time. Record the exact booted kernel and bundle before changing it. If the lone indication is a crash, keep the possible of unintended trigger or an unrelated bug during motionless patching promptly.

Patch and mitigation strategy

The preferred remediation is a vendor kernel containing the RCU reclamation fix, followed by a reboot into that kernel. Use the distribution’s normal update scheme and its advisory. Avoid cherry-picking a sole mainline commit into an endeavor kernel unless the kernel vendor or an informed kernel engineering squad owns the resulting build. Stable branches may necessitate connected context, and unsupported tradition kernels create forthcoming place and assistance risk.

For a fleet, position systems by community reachability, MPTCP usage, petition migration, endeavor criticality, tenant exposure, and vendor support. Begin alongside internet-facing nodes and infrastructure that terminates ample volumes of untrusted TCP. Patch redundant members in a rolling sequence: drain connections, update, reboot, verify the operating kernel, execute assistance checks, and come back the node to rotation before continuing.

Where contiguous reboot is impossible, decrease exposure. Disable MPTCP if the institution does not use it. Restrict inbound TCP to required sources and ports. Move administration services rearward authenticated gateways. Remove unused community listeners. Apply charge controls or SYN proxying at an upstream equipment anywhere operationally safe. These measures can decrease opportunities and defend the particular public-research path, but they do not accurate the old pointer.

Evaluate net.ipv4.tcp_migrate_req and reuseport BPF lone alongside the assistance owner. Turning off petition immigration may decrease one affected way but can alter failover behavior. Removing a BPF program may alter traffic distribution. Configuration changes need functional evaluation and a rollback plan.

Blocking all IPv4 options at an border may decrease visibility to paths that depend on choice data, but it is an incomplete and possibly disruptive control. Some networks use options for specialized behavior, and the exact association between a display and all susceptible way must be established. Middleboxes can normalize or terminate connections in ways that differ from uncomplicated packet filtering. Use specified controls as impermanent hazard decrease only.

Do not depend on receptacle restarts, use redeployments, or user-space archive updates. The susceptible code runs in the presenter kernel. Do not assume that a web use firewall sees or understands the applicable IP and TCP handshake state. A WAF that starts handling following a TCP association is established is downstream of the susceptible operation.

Unsupported kernels current a straightforward decision. Move the workload to a supported build or isolate it until replacement. A locally patched kernel can be suitable for specialized products, but it requires owners who can validate the backport, test networking behavior, keep symbols, publish provenance, and provision forthcoming fixes. For most organizations, moving to a vendor-supported kernel is safer and faster.

Penligent can assistance authorized validation by assisting safety teams arrange exposed-service discovery, configuration evidence, and retesting about a controlled place window. The goal for this kernel matter is not to reproduce a distant base sequence on production. It is to demonstrate which resources were reachable, which vendor fix they received, and whether the assistance remained fit following the corrected kernel booted.

Verify that remediation really worked

A prosperous update job is not the identical as a remediated host. Verification starts following reboot. Confirm the energetic kernel alongside uname -r and map it to the vendor’s fixed package. Confirm the update installed on the expected footwear partition and that the bootloader did not autumn rear following an error. Check that secure-boot guideline accepted the depiction anywhere applicable.

Validate the assistance from the two sides of its rely boundary. An inner health inspect may continue during the community listener is absent, and a community inspect may continue during a personal backend way is broken. Exercise normal TCP association establishment, TLS negotiation, protocol health, and delegate requests. For MPTCP services, use the organization’s normal MPTCP functional test without antagonistic timing or memory-corruption attempts.

Review kernel logs for warnings introduced by the rollout. Network fixes can engage alongside drivers, offload, BPF, burden balancing, and tradition modules. A regression does not validate returning indefinitely to a susceptible kernel. Follow the vendor’s rollback or replacement guidance, use impermanent visibility reduction, and escalate for a corrected package.

Rescan alongside a tool that understands vendor backports. If the scanner motionless flags the asset, nexus the vendor advisory, installed bundle version, running-kernel evidence, and fix provenance. Suppress lone the exact finding for the exact build, alongside an expiration or assessment date. Broad exceptions according to an upstream type difference can conceal afterward susceptible nodes.

For Kubernetes and autoscaling fleets, verify templates as fine as current instances. An old device depiction can recreate susceptible nodes following the first rollout. Update initiate templates, node images, aureate images, improvement media, and disaster-recovery definitions. Test a scale-out event and verify the new node boots a fixed kernel.

For appliances, verify that the firmware upgrade changed the applicable kernel build. Keep the vendor bulletin and firmware checksum. If the appliance vendor has not published a fix, document compensating controls and get a assistance statement. Avoid assuming that a firmware publish date following the upstream place automatically includes it.

Close the remediation item lone whenever all of the following are true:

• The asset and its genuine TCP visibility are recorded.
• The vendor identifies the installed build as fixed or not affected.
• The fixed kernel is running, not merely installed.
• The required reboot or vendor-approved live-patch activation completed.
• Critical services passed post-change tests.
• Images, templates, and replacement-node sources were updated.
• Temporary mitigations and exceptions have owners and expiration dates.
• Evidence is retained for event reply and audit.

Common appraisal mistakes

The archetypal error is treating “Linux” as one product. The kernel is shipped through distributions, haze images, embedded firmware, managed node images, and tradition builds. Each may transport distinct backports. Use the exact merchandise channel.

The second error is equating a CVSS mark alongside utilize prevalence. A 9.8 basis mark describes specialized severity under a metric model. It does not figure susceptible hosts or demonstrate energetic exploitation. A 5.9 vendor mark does not negate a prosperous lab utilize against another configuration. Risk combines severity, exposure, evidence, asset value, and accessible controls.

The third error is study the Anthropic outcome as universal. The investigation proves that a capable squad could utilize a susceptible MPTCP listener remotely in its lab. It does not established identical behavior for all TCP listener. Use it to prioritize MPTCP and exposed networking, not to create unsupported claims.

The fourth error is declaring IPv6 universally safe. The chief child-socket transfer matter is IPv4-specific, during the upstream clarification separately calls out an IPv6 immigration involvement involving CALIPSO. Dual-stack systems additionally continue to disclose IPv4. Evaluate the two protocols and prosecute consequent vendor fixes.

The fifth error is scanning lone use containers. Container images do not transport the energetic presenter kernel in the normal model. Inventory and place nodes. Serverless and managed-container customers should consult the provider, since the provider controls the kernel equal whenever customers authority images.

The sixth error is attempting community utilize code as a manufacturing test. Winning the competition intentionally can collision or colony the machine. It additionally provides small additional endeavor value formerly the vendor has confirmed that the build is vulnerable. Safe configuration, package, exposure, and post-patch checks provision actionable evidence without weaponizing the flaw.

The seventh error is decision the ticket following facility without rebooting. The old kernel remains energetic until the scheme boots the new depiction unless a vendor-supported live-patch scheme covers the CVE. Always document the runtime result.

Frequently asked questions

Does CVE-2026-98432 authorize distant base admission on all Linux server?

• No. The bug is network reachable and a controlled investigation utilize achieved base command implementation against a susceptible MPTCP listener.
• Exploitability depends on kernel build, configuration, architecture, hardening, allocator behavior, assistance exposure, and competition reliability.
• Every affected, reachable presenter should motionless be patched since the underlying flaw is kernel recollection corruption.

Why does the CVE document say 9.8 during Red Hat says 5.9?

• The CVE mark expresses an upstream worst-case basis vector alongside network access, no privileges, no interaction, and elevated possible impact.
• Red Hat scores the matter for its products and considers the competition complexity, shipped configuration, and apt applicable outcome.
• Use the vendor appraisal for bundle position and the broader evidence for prioritization.

Is IPv6 affected?

• The chief matter in tcp_v4_syn_recv_sock() is particular to IPv4 since the average IPv6 way duplicates options.
• The upstream clarification identifies a distinct IPv6 request-migration involvement whenever CALIPSO options are used.
• Follow the vendor’s complete advisory fairly than applying a covering “IPv6 safe” label.

Does disabling MPTCP fix the vulnerability?

• No. It removes the configuration used by the community remote-code-execution display and can decrease contiguous hazard if MPTCP is unused.
• The underlying life error additionally concerns IPv4 TCP petition and kid socket handling.
• Install the corrected vendor kernel.

Do containers need to be rebuilt?

• The normal receptacle example shares the presenter kernel, so the node or presenter must obtain the kernel fix.
• Rebuilding an use depiction solitary does not remediate the issue.
• Update node templates and managed-cluster images so autoscaling does not recreate susceptible hosts.

How should a backported fix be verified?

• Use the distribution’s CVE page, erratum, bundle changelog, or VEX declaration for the exact merchandise and kernel flavor.
• Confirm the fixed bundle is installed and that uname -r shows the corresponding operating kernel following reboot.
• Do not necessitate the upstream first-fixed type whenever the vendor documents a backport.

Should defenders run an utilize evidence of concept?

• Production exploitation tests are unnecessary and can collision or colony the host.
• Validate kernel provenance, exposure, MPTCP and immigration settings, vendor status, reboot completion, and assistance health.
• Use disposable, authorized lab systems for any memory-safety research.

What evidence suggests an attempted exploit?

• Relevant kernel crashes or sanitizer findings near IPv4 choice building and socket demolition are powerful specialized clues.
• Repeated different handshake attempts against a susceptible MPTCP listener can addition suspicion but are not proof.
• Correlate network behavior alongside kernel logs, collision dumps, root-level procedure anomalies, and the exact susceptible build.

Final protective priorities

CVE-2026-98432 is a genuine kernel object-lifetime nonaccomplishment alongside a straightforward upstream correction and a demonstrated high-impact investigation outcome. Its hazard should neither be reduced to a theoretical collision nor inflated into a assertion that all Linux server is already remotely exploitable. The accessible evidence supports urgent, targeted action.

Prioritize exposed MPTCP listeners and internet-facing Linux TCP ending points. Use vendor bundle data fairly than generic type matching. Apply the corrected kernel, reboot, validate assistance operation, update node and appliance templates, and maintain evidence of the operating fix. Where a alter opening cannot open immediately, disable unused MPTCP, narrow TCP exposure, and detect applicable kernel and handshake behavior during scheduling the update.

The most crucial specialized instruction is broader than this CVE: RCU safety is a agreement between readers and reclaimers. A audience fastener cannot defend an entity that a author returns immediately to the allocator. The place restores that agreement by waiting for readers before freeing shared IP options. Verification should reconstruct the operational agreement as well: the institution knows which hosts were exposed, which fixed code they run, and whether the assistance motionless plant following remediation.

Operational notes for MPTCP and dual-stack services

MPTCP inventory is frequently small apparent than average TCP inventory since administrators may cognize that the kernel supports the protocol without knowing which use binds an MPTCP socket. Start at the operating-system layer, afterward ask assistance owners whether they explicitly create MPTCP sockets or depend on a archive or proxy that negotiates subflows. Review assistance units, receptacle capabilities, socket activation, and deployment configuration. A host-level enabled emblem is a clue, not a complete assistance map. Conversely, an use that can use MPTCP may autumn rear to average TCP in one surroundings and actively hear alongside MPTCP in another.

For all applicant service, document the location families and interfaces anywhere the listener is bound. A listener border to a wildcard location may be reachable through additional interfaces than its assistance configuration suggests. Host firewall rules, haze safety groups, network policy, and upstream burden balancer behavior all contribute. A helpful document says whether an untrusted client can complete a way to the host’s TCP stack, whether a proxy terminates the client association first, and whether inner clients are in scope. This makes it imaginable to distinct a really secluded assistance from one that is merely absent from the community DNS zone.

Dual-stack deployments have to be assessed as two connected but distinct paths. Inventory IPv4 and IPv6 routes, listeners, safety groups, and translation devices independently. The upstream bug’s chief ownership transfer is in IPv4 code, but a presenter alongside IPv6-only community ingress can motionless disclose IPv4 through a administration VLAN, collection overlay, health-check network, or local peer. An IPv6 packet may additionally be translated or proxied into a distinct IPv4 association before reaching the susceptible host. Network architecture, not a merchandise tag specified as “IPv6-only,” determines what the kernel processes.

Do not disable a protocol throughout an complete fleet before identifying dependencies. MPTCP may be part of an intentional movement or path-resilience design. A hasty alter can logic throughput loss, interrupt failover, or alter association behavior in ways that create an event harder to diagnose. Where MPTCP is not used, disabling it is a sensible impermanent decrease in exposure, but document the alter and verify that the assistance has not silently depended on it. Where it is used, prioritize a vendor kernel rollout and use network restrictions compatible alongside the assistance objective.

Plan kernel changes about association state

Kernel care on network endpoints has an preparedness dimension. A reboot interrupts established connections, resets connection-tracking province on several appliances, and may alter routing or offload behavior. Before updating a load-balanced service, verify that the remaining fit nodes have adequate capacity. Drain one node at a time, delay for long-lived sessions to near or attain an accepted timeout, update the kernel, reboot, and verify preparedness before returning it to rotation. If the assistance uses MPTCP throughout multiple paths, contain way failover behavior in the alter test.

For stateful firewalls and gateways, verify how the phase handles association synchronization during rolling maintenance. A node may be fit at the procedure flat but not prepared to obtain traffic since routes, tunnel state, or conntrack synchronization has not converged. Include a inspect from a delegate client network, not fair a local health endpoint. Keep the former depiction accessible according to the vendor’s supported rollback process, but create certain any rollback triggers the impermanent visibility controls described in the hazard record.

Coordinate place windows alongside kernel extensions and out-of-tree modules. Storage, observability, security, and network agents can forestall a new kernel from booting or can endure functionality following an update. Verify that required modules have compatible builds and signatures. A unsuccessful reboot into the old depiction may depart the presenter susceptible during monitoring shows lone that the bundle director completed successfully. Alert on a mismatch between the expected fixed build and the runtime kernel following maintenance.

In haze fleets, update the origin depiction before replacing instances. A one-time restart of operating virtual machines is insufficient if autoscaling groups, case templates, improvement plans, or managed node pools motionless mention to an old image. Test a newly launched replacement in the identical network and verify the vendor kernel is active. For immutable infrastructure, the remediation component is frequently the depiction affirmative the rollout policy, fairly than an idiosyncratic presenter package.

For Kubernetes, coordinate node eviction alongside workload disruption budgets and persistent retention constraints. Update a canary node first, verify CNI and assistance routing, afterward continue throughout zones. DaemonSets and privileged agents have to be checked for kernel-version compatibility. The fact that a receptacle restarts onto a patched node does not demonstrate all replica moved; collect node-level evidence and tie all workload rear to its current node. Managed Kubernetes customers should use the provider’s node depiction and care direction since the provider owns the kernel build.

Use evidence that survives a afterward audit

A defensible remediation document ties the advisory to a particular artifact. Save the vendor’s CVE leaf or erratum, the bundle name and revision, the presenter or depiction identifier, the footwear period following the update, and the operating kernel string. Where the vendor publishes source-package status, contain the exact kernel sensation and release. Where a merchandise bundles a tradition kernel, contain the appliance firmware type and vendor statement. This prevents a afterward reviewer from having to infer whether a generic “Linux updated” note covered all system.

For organizations that create SBOMs, nexus the kernel bundle to the affected asset inventory and maintain a VEX declaration whenever available. A VEX document can say that a merchandise is affected, not affected, fixed, or under investigation, and can explain the basis for that status. It is particularly helpful whenever an upstream CVE repository shows a broad affected range during a allocation has backported the change. The declaration should remain scoped to the exact merchandise release; do not reuse a decision throughout a distinct kernel sensation without evidence.

Keep the first and updated scan results. A before-and-after difference can display that the scanner recognized a vendor bundle revision, but it should not substitute the vendor mapping. If a scanner continues to study the CVE following an update, document whether the finding is a old inventory result, an unsupported kernel, a missing reboot, or a false affirmative because of backport handling. A closed finding alongside no clarification is difficult to defend and uncomplicated to reopen incorrectly.

Track exceptions alongside an owner, endeavor reason, compensating controls, mark date, and definitive re-evaluation condition. An elimination for a temporarily unavailable appliance should acknowledge the network paths it can receive, the services exposed, and whether MPTCP is active. Set an expiration fairly than making the elimination permanent. Reassess sooner if the vendor publishes a fix, new utilize evidence appears, or the appliance’s network border changes.

Decision guide for safety teams

When the safety squad receives a CVE alert, the archetypal decision is whether the institution owns a applicable kernel, not whether a exposure scanner has already produced a finding. Query endpoint management, haze inventory, virtual device images, Kubernetes node pools, network appliances, and embedded merchandise records. Search for the kernel bundle and supported OS family. A origin repository or runtime tag can assistance find systems, but verify it against the genuine operating fleet.

The second decision is which resources can obtain untrusted TCP traffic. Use haze stream logs, burden balancer configuration, firewall policy, assistance maps, and presenter listeners together. Distinguish straightforward net traffic from traffic terminated by a managed proxy. Include trusted inner networks in the danger example since compromised workstations and workloads can rotate into untrusted sources. A control-plane-only appliance may motionless have a data-plane interface reachable from client networks.

The third decision is whether any circumstance elevates the priority. An MPTCP listener, petition migration, reuseport BPF, community exposure, high-value network role, or deficiency of dependable presenter monitoring should move the scheme before in the queue. These conditions do not demonstrate exploitation. They acknowledge configurations that are nearer to the known specialized way or have higher endeavor effect if compromised.

The fourth decision is how to validate closure. Identify the supported fixed package, deploy it, restart into it, test network services, and difference the final province against the advisory. Do not obtain a planned care ticket or a downloaded bundle as closure. The runtime province is the evidence that matters. If the place cannot be applied, document a time-bounded elimination and decrease reachable paths during the institution obtains a supported fix.

Finally, decide whether an event inquiry is needed. A susceptible community MPTCP listener solitary warrants urgent patching; it does not by itself demonstrate compromise. Add event reply whenever there are applicable kernel faults, doubtful long-running association attempts, unexplained base activity, integrity changes, or dependable danger intellect particular to the affected service. Keeping place administration and event reply connected but distinct avoids the two complacency and unsupported breach declarations.

How to communicate the hazard accurately

Executive updates should province the affected asset count, reachable assistance count, MPTCP exposure, fixed-build availability, rollout progress, and unresolved exceptions. Avoid presenting the CVSS 9.8 figure without noting the product-specific 5.9 appraisal and investigation conditions. The figure is a helpful severity signal, but decision-makers need to cognize what their own surroundings really runs and exposes.

A concise specialized declaration can say: “The Linux IPv4 TCP petition way can use IP-options recollection following it has been freed. The upstream fix defers reclamation through RCU. Anthropic demonstrated distant base code implementation against a susceptible MPTCP listener in a controlled lab; this does not established worldwide exploitability. We are patching internet-facing and MPTCP-enabled systems archetypal and verifying the operating vendor kernel following reboot.” This formulation communicates consequence, evidence, boundary, and act without overstating what is known.

Customer-facing communications should prosecute the organization’s event and exposure disclosure policy. Do not assertion a client scheme is susceptible solely since it runs Linux. Ask the phase or vendor for the exact kernel position and province whether a fixed build is available. If assistance break is required for a reboot, communicate the care effect separately from utilize evidence.

Security teams should additionally maintain uncertainty. If a vendor has not yet assessed a tradition image, say that position is under inquiry and acknowledge whenever it volition be reviewed. If an MPTCP listener is not found, document the evidence and period of inspection. If the scheme is patched but a scanner has not recognized the backport, nexus the vendor evidence and keep the finding in a reviewable province until asset data converges.

Read next

Lean 4 for the JavaScript and WebAssembly world. Lasm compiles average Lean 4 programs onward of period to WebAssembly. One Lean code basis can rotate into a Node server, a serverless or border function, a WASI/Fastly component or a browser app. Because it is Lean, you can demonstrate properties of the code you deploy. The flagship example, Conduit, is the RealWorld app with 117 proved theorems. Lasm ships on npm and brings Lean, Lake and its build tools alongside it; you lone need Node (or Bun or Deno).

npm create @lasm@latest my-app -- --template hono # then: cd my-app && npm instal && npm run dev

AI agents: this README is complete on its own. llms.txt is the short index, and docs/AI.md lists the rules that preserve you from incorrect turns.

If Lasm is helpful to you, I'd value your sponsorship (more below).

Every row is tested in CI alongside the platform's own local runtime, depiction or emulator. By project guideline CI never deploys to a genuine haze account (how all is tested).

Node builds have Lean's complete runtime (threads, files, processes, sockets). The edge, Bun/Deno, WASI and browser builds run Lean single-threaded, without sockets or processes (and without files, apart from on WASI); the remainder of Lean works.

Every example has a README alongside a one-command run; examples/README.md lists them all.

examples/conduit is Conduit, the RealWorld app (a Medium clone), written entirely in Lean: the REST API, the server-rendered browser app and the proofs.

• 117 theorems concerning the code that really runs, checked alongside no apologetic and only Lean's norm axioms (npm run proofs; PROOFS.md lists all one in plain English). They shield authority (only authors change their articles and comments), follows and favorites, slugs that never collide, pagination that never skips or repeats, validation shared by client and server (the app never sends what the server would reject), JSON circular trips and Markdown nexus safety. The endpoints are written against a Store of functions, and the proofs run that identical code on a example of the tables.
• What is trusted, not proved: that all SQL declaration does what its model says, the JSON content layer, concurrency between requests, and Lean, Lasm and the JavaScript runtime. Conformance to the entire RealWorld spec is tested, not proved.
• API: the authoritative RealWorld API suite passes unmodified (13 of 13 files, 154 requests) on Node (node:sqlite), Cloudflare Workers (D1) and Bun (bun:sqlite). Each mark has one hand-written @[js] binding module.
• Frontend: Lasm.UI on RealWorld's authoritative templates, alongside server-side rendering, hydration and Markdown parsed in Lean. The authoritative Playwright end-to-end suite passes alongside no retries on Node alongside Chromium, Firefox and WebKit, and on Workers and Bun alongside Chromium.

All of this runs in CI (conduit.yml, run 40615274657, with @lasm/cli 0.3.4).

cd examples/conduit npm instal # @lasm/cli, Hurl and Playwright (the authoritative suites' runners) npm run build && npm commencement # http://localhost:3000: the app and its API on Node npm run proofs # inspect all 117 theorems npm test # the authoritative API suite (also test:workers, test:bun) npx playwright instal chromium && npm run test:e2e # the authoritative end-to-end suite npm run build:workers && npx wrangler dev # Cloudflare Workers alongside local D1 npm run build:bun && npm run start:bun # Bun alongside bun:sqlite

A sole document needs no project. Save this complete program as Main.lean:

def main : IO Unit := do IO.println s!"Hello from Lean! 2 + 3 = {2 + 3}"

npx @lasm/cli Main.lean # builds and runs: Hello from Lean! 2 + 3 = 5 npx @lasm/cli build Main.lean # writes dist/; run it with: node dist/main.mjs

The archetypal build on a new device fetches Lean and the build tools formerly (about 250–275 MB; 19 s for that archetypal build on the Linux CI runner). Later dev builds of a one-line alter obtain concerning 1–2 s.

Each formula is complete: create, develop, build, deploy. Lasm never installs or starts a platform's own CLI (wrangler, vercel, fastly, …); you run those. npm run dev is lasm dev: it rebuilds concerning 2 s following all preserve and restarts the server, and keeps the final fine build operating whenever there is a category error.

Node server (Hono; additionally express, fastify, std-http, fetch).

npm create @lasm@latest my-api -- --template hono cd my-api && npm install npm run dev # http://localhost:3000/hello/Ada npm run build && npm commencement # dist/ needs lone Node 24+ docker build -t my-api . && docker run -p 8080:8080 my-api # the generated Dockerfile

AWS Lambda / Vercel / Netlify / Azure / Google Cloud Functions.

npm create @lasm@latest my-fn -- --template hono --deploy lambda-zip # or vercel, netlify, azure, gcf, lambda-edge cd my-fn && npm install npm run build:lambda # dist/ and lambda.zip (handler lasm-lambda.handler) # deploy lambda.zip alongside the AWS console, aws CLI or SAM; recipes: docs/deploy/lambda.md

Cloudflare Workers (and Vercel Edge, Netlify Edge, Deno Deploy, Supabase).

npm create @lasm@latest my-edge -- --template hono --deploy workers cd my-edge && npm install npm run build:workers # workers/ (wrangler.toml came from lasm init) npx wrangler dev # local workerd; npx wrangler deploy to publish

Fastly Compute, WASI, Spin.

npm create @lasm@latest my-svc -- --template fetch --deploy fastly --deploy spin cd my-svc && npm install npm run build:fastly && fastly compute assist # Viceroy on http://127.0.0.1:7676 npm run build:wasi-http && rotation up # or: wasmtime assist wasi-http/main.wasm

Browser app.

npm create @lasm@latest my-web -- --template web cd my-web && npm install npm run dev # http://127.0.0.1:5173, live reload npm run build # dist/: a fixed location for any presenter or CDN

Full stack (server + browser + verified API).

npm create @lasm@latest my-app -- --template fullstack cd my-app && npm install npm run dev # one URL: http://127.0.0.1:3000 npm run build && npm commencement # Node; additionally build:workers, build:bun, build:deno

Editor. Run npx lasm publishing company formerly per project; lasm init, lasm dev and lasm build additionally do it. The Lean publishing company (VS Code's Lean 4 extension) afterward resolves import Lasm.* (details).

The fullstack template is one Lean project alongside a server (Lasm.Fetch), a browser app (Lasm.UI) and the API between them (Lasm.RPC). The regulation a request must fulfill is written and proved once, in Shared.lean, which the two sides import (templates/fullstack):

-- Shared.lean @[irreducible] def checkTitle (title : String) : Except String Unit := let n := (clean title).length if n = 0 then .error "Write item first." else if n > maxTitle then .error s!"Keep it under {maxTitle} characters." else .ok () /-- Proved once, holds in the browser and on the server. -/ theorem checkTitle_ok {title : String} (h : checkTitle heading = .ok ()) : 0 < (clean title).length ∧ (clean title).length ≤ maxTitle := by unfold checkTitle at h by_cases h0 : (clean title).length = 0 · simp [h0] at h · by_cases h1 : (clean title).length > maxTitle · simp [h0, h1] at h · omega def addTodo : Endpoint NewTodo Todo := { name := "addTodo", validate := fun r => checkTitle r.title }

-- Server.lean: storing a todo demands the evidence that its heading passed the check, -- and `addTodo.serve` hands the handler that evidence (`ok`) following re-validating. def Store.add (s : Store) (title : String) (_ : checkTitle heading = .ok ()) : Store × Todo := let t := { id := s.next, heading := spotless title, done := false } ({ todos := s.todos.push t, next := s.next + 1 }, t) addTodo.serve fun req ok => do let (s, t) := (← burden kv).add req.title ok preserve kv s come back .ok t

-- Client.lean: a theorem concerning the browser app: it never sends an invalid title. theorem add_invalid (m : Model) (e : String) (h : checkTitle m.draft = .error e) : (update .add m).2.effects = [.msg (.added (.error (.invalid e)))] := addTodo.call_invalid { heading := m.draft } Msg.added "" e h

Where proofs live and how they are checked.

Not proved, tested in CI instead: the JSON/HTTP transport between client and server, the JavaScript that applies patches to the genuine DOM, the Lasm compiler and runtime, and the browsers. Lean's own compiler is trusted, as in any Lean program (UI.md, RPC.md).

Declare all JavaScript function you call alongside one line; the Lean category says how values convert. A complete program (Node's earth fetch):

import Lasm.JS open Lasm.JS /-- `await fetch(url, init)` (Node's earth fetch) -/ @[js "globalThis" "fetch"] opaque fetch : String → Data → IO Value def main : IO Unit := do let reply ← fetch "https://example.com" (obj []) IO.println s!"{← response.get "status" Nat}: {(← response.callMethodAwait "text" #[] String).length} characters"

The rules for penning bindings:

• @[js "module" "export"] opaque name : A → B → IO R binds module.export. The module is an npm bundle ("marked"), a Node built-in ("node:fs"), or "globalThis" for globals. "new Hono" calls a constructor, and "" is the module's own value.
• End the category in IO R for a value returned at formerly and in Async R for a promise. An Async binding is awaited without holding a Lean thread.
• Use String, Nat, Int, Float, Bool, ByteArray, Array, List, Option, tuples, Data (any JS data) or Value (a JS entity reference: get, callMethod, callMethodAwait). Your own structures change alongside deriving ToJS, FromJS.
• Function.ofFn / Function.ofFnReply rotate Lean functions into JS callbacks. Framework handlers use them (see the hono, province and fastify templates).
• npm instal the bundle next to the lakefile. lasm build checks all binding against the installed bundle (Lasm.JS binding inspect failed: … export "x" is missing) and copies manufacturing requirements into dist/node_modules.
• Each call crosses from a Lean thread to Node's chief thread (about 24 µs), so prefer one coarse call complete many small ones.

Full guide, alongside Express, Hono, pg, jose and fetch examples and an agent checklist: docs/JS_BINDINGS.md.

All numbers are from CI on a liberated GitHub runner (4-CPU AMD EPYC, Linux x64), candidate 0.1.0-experimental.40494203854 (2026-10-27) unless another run is named. Full tables, method and caveats: BENCHMARKS.md.

Lean on Node pays for WebAssembly and its threads. A chilly commencement is CPU-bound, so it grows on small serverless CPU shares, and all JavaScript call crosses threads. Pure-Lean Std.Http on Node is dilatory (1,290 req/s), so use Hono, Express, Fastify or Lasm.Fetch for manufacturing HTTP. Arithmetic on numbers alongside thousands of digits is slower than native Lean (no GMP).

• Ahead of period only. A deployed program cannot elaborate, measure or compile Lean, burden component data or plugins, or use Lean's C++ compiler/kernel at run time (exact list). Proofs, tactics, macros and #eval run during compiling, as usual.
• Lean 4.35.0 exactly. Other lean-toolchain versions are rejected alongside a message.
• Node: provision an app at smallest 512 MB; it reserves concerning 22 GB of virtual address space. Prebuilt native libraries (-l, shared libraries) cannot be linked; a package's bundled C origin is compiled for you.
• Edge, Bun/Deno, browser, WASI: single-threaded Lean; no sockets, processes or signals; no records apart from on WASI. In the browser, blocking waits halt the app unless it is built alongside --suspend jspi for a browser alongside JSPI; use Async.
• No premade bindings for npm packages; Lasm.Web covers the center web platform.
• Editor: Lasm.* imports determine in the publishing company following npx lasm publishing company (above).
• Platforms: no Windows ARM64 and no Alpine/musl build machines (built apps run on Alpine). Hosted platforms are tested alongside their local tools, never alongside a real account.

• Start: Getting started · All documentation · For AI agents · llms.txt
• Guides: servers and npm interop · serverless and containers · edge · Bun and Deno · browser and Lasm.UI · full stack (Lasm.RPC) · Lasm.Fetch · WASI and Fastly · the edit loop
• Evidence: benchmarks · where apps run · language coverage · compatible Lean packages · decisions

If Lasm is helpful to you or you desire to see it succeed, I'd value your sponsorship: github.com/sponsors/lastmjs. It supports me and the activity on Lasm and the another Millillion projects. My archetypal goal is $250 a month, adequate for one dedicated Claude Code account for Lasm. You can additionally assistance by leading the repo, trying it, and reporting what breaks.

Everything below is the exact contract: all command and option, supported machines and platforms, and exactly what a deployed Lean program cannot do.

Install in a project alongside npm instal -D @lasm/cli (the bin is lasm), or run without installing: npx @lasm/cli Main.lean. npm create @lasm runs lasm init of the identical @lasm/cli type alongside the arguments unchanged. With the Main.lean from the quick start:

npx lasm Main.lean # build (dev profile) and run: Hello from Lean! 2 + 3 = 5 npx lasm build Main.lean # compose dist/ (release profile) npx lasm --version # version, Lean, runtime and phase (for bug reports) node dist/main.mjs # run the deployment: lone Node is needed npx lasm build Main.lean --target lambda # dist/ and an AWS Lambda zip

--rebuild and --verbose activity alongside run and build. --output and --target are build-only; arguments following -- are run-only. The application's exit position is preserved. npx lasm --version (-v) prints the version, Lean release, JavaScript runtime and phase (include it in bug reports). There is no install, spotless or uninstall subcommand.

Build profiles. Both nexus the identical program alongside the identical libraries and are deterministic. release (lasm build, lasm Main.lean --release): the full Binaryen size optimization; byte-reproducible; the one to deploy. dev (lasm Main.lean, lasm dev, lasm build --dev): leaves those passes out and compiles your modules at -O1; it behaves the same, builds multiple seconds faster, and its program.wasm is concerning 15–20 % larger. A dev rebuild starts from the project's former build, so its bytes can depend on that build. build-info.json records "profile". lasm bundle and lasm build --dev --target <platform> refuse a dev build unless you continue --allow-dev.

Environment variables (all optional):

Other LASM_* variables in the origin are maintainer diagnostics, not a supported interface.

Installation. npm instal @lasm/cli brings Lean and the build tools as exact-pinned @lasm/… npm packages for your phase through your own registry, proxy and cache. The Lake/Lean-import data and, lone for Lake projects alongside C code, the C tier (@lasm/lean-c-<platform>) are fetched alongside your npm on archetypal use. The terminal shows progress; afterward builds reuse verified tools and unchanged outputs. On a new machine, without the download, a archetypal Hono build took 25.7 s (Linux x64), 27.8 s (Linux arm64), 44.4 s (Windows), 58.7 s (Apple Silicon) and 141.9 s (Intel Mac) on the CI runners (build time, run 40131930601). Cache locations and recovery: NODE_SUPPORT.md, INSTALLATION_HARDENING.md. Git is needed lone for Lake projects alongside Git or Reservoir dependencies; Lasm uses the git on your PATH and says how to instal it whenever it is missing.

Existing Lake projects build alongside npx lasm build Main.lean from the project directory. Pin leanprover/lean4:v4.35.0 in lean-toolchain; another versions are rejected alongside Unsupported Lean toolchain … Lasm supports Lean v4.35.0. A per-package compatibility list covers Batteries, Cli, LSpec, Plausible, Aesop, Qq, leansqlite, UnicodeBasic, MD4Lean, lean-zip, lean4-parser, lean-redis and others; packages not on it are untested.

Machines that build alongside Lasm (the compiler):

Node 24 or newer (tested: 24.0.0, 24.22.1, 26.12.1). No motor flags. Exact tested artifacts: NODE_ACCEPTANCE.md.

A Node dist/ needs Node 24 or newer (Node 22 and older halt alongside This use requires Node 24.0.0 or newer) and at smallest 512 MB of memory. It runs on Linux x64 and arm64 (glibc 2.28+, or musl/Alpine) from a build on any supported platform, and on the build machine's own platform. Copy all of dist/; no Lean source, npm instal or build tools are needed there. Each phase below is tested in CI alongside the local runtime, depiction or emulator named; none alongside a real cloud account. Full matrix: DEPLOYMENT.md.

A dist/ built on Windows and copied to Linux another than through docker build needs chmod 755 dist/host/native/process/linux-*. Node's --jitless cannot work (it disables WebAssembly). Hosts that cap virtual recollection (ulimit -v, vm.overcommit_memory=2) refuse the Node build, which reserves concerning 22 GB of address space. Node 26's authoritative binary needs libatomic1 on minimal images that install the tarball themselves.

Builds enforce ahead-of-time execution. Ordinary functions, recursion, closures, inductive types, form matching, category classes, reliant types and compiled IO are supported. Imports, macros, elaboration, tactics, deriving, proofs and #eval run during compilation in managed native Lean. Initializers count as runtime dependencies: a broad import Lean can keep the compiler; use meta import Lean whenever lone macros or strategies need it, and narrower imports for runtime data libraries (import Lean alongside Lean.Json, and deriving ToJson, FromJson, build and run). Each rejection is explained: Lasm prints the sequence from your code to the compiler code and, whenever a broad import is the cause, the narrower modules your code uses. Deployed programs regard LEAN_ABORT_ON_NONLINEAR=1 as native Lean does. Per-platform results: language coverage.

The deployed use cannot use:

The build checks reachable runtime dependencies, including imported libraries and indirect calls; a reachable forbidden call is rejected equal if your input would not obtain that branch, and deceased code removed by the linker does not count. The launcher additionally rejects missing, old or incompatible capability records before loading the use (a consistency check, not a safety sandbox). There is no large compatibility fallback.

Lake packages. Modules imported lone for compilation (tactics, elaborators, for example Aesop, Qq or import Lean for macros) do not keep Lean's compiler in the deployment. Lasm runs a module's initializers lone whenever the program uses something they define or register, or whenever they are the program's own code doing IO or calling C (--verbose shows how many were skipped). C origin that a package bundles (extern_lib, moreLinkObjs, for example leansqlite's SQLite) is compiled with Lean's own clang, fetched formerly as the C tier (39–52 MB); no scheme C compiler is needed (macOS needs the Xcode Command Line Tools SDK for C archive headers). Prebuilt native libraries (shared libraries, -l options: libcurl, OpenSSL, libpq, BLAS) cannot be linked; the build names the archive and the package.

Not publish guarantees. Console output, arguments, exit codes, local Lake imports and selected language/filesystem fixtures have native-versus-Node tests, and before 0.1.0 Lean's runtime-capable upstream suite and 19 ecosystem projects ran on all five platforms alongside zero regressions against the former accepted candidate (0.1.0 gate). Complete IO.FS, concurrency, subprocess/signal/terminal parity, all third-party archive and the complete upstream suite are not guaranteed (IO gaps). Big numbers (Nat/Int beyond 63 bits) use Lean's own arbitrary-precision code alternatively of GNU MP, so apps contain no LGPL code; results equal native Lean's, but at 10,000 digits multiplication is concerning 5× and Nat.gcd concerning 60× slower than alongside GMP in Wasm (numbers). Lake dependencies use your scheme Git (system Git).

0.1.0 was the archetypal npm publish (notes); 0.2.0 adds edge targets and Bun/Deno (notes); 0.3.0 adds the browser, Lasm.UI, full-stack apps, WASI/Fastly and the publishing company support (notes); 0.3.1 puts the starter code under MIT-0 and adds bug-report pointers (notes); 0.3.2 fixes Std.Internal.UV sockets, timers and signals (notes); 0.3.3 was never published, and its changes shipped in 0.3.4 (notes); 0.3.5 updates the README and the Conduit example (notes). Lasm's npm packages (@lasm/cli, @lasm/create and the @lasm/… tool packages) are published lone by the release.yml workflow, through npm trusted publishing alongside provenance: no npm tokens exist. A publish is a pull petition that bumps the package.json type and is published lone following the release-checks position (five-platform applicant checks; edge, Bun/Deno, browser, Lasm.UI, WASI/Fastly, fullstack, component and dev-loop checks; and an npm rehearsal of the exact packages) passed for the released commit. Found a bug? npx lasm --version gives the type row the bug study form asks for. npm perspective @lasm/cli@<version> shows the provenance, and npm audit signatures in a project verifies it. Details: RELEASING.md.

Lasm's own origin is under the MIT License (copyright Jordan Last). The starter code — everything lasm init and npm create @lasm put in a new project, templates/, examples/ and the code samples in this README and docs/ — is additionally under MIT No Attribution (MIT-0), in every version: it is yours, no attribution needed. @lasm/create is MIT, and @lasm/cli's licence site is an SPDX expression of Lasm's MIT, MIT-0 and every component it bundles, alongside their texts in licenses/. The license audit lists all distributed component, its license and how all duty is met.

• Built dist/. THIRD_PARTY_NOTICES.txt starts alongside Lasm's MIT notice and the catalog of Lean records Lasm changed, afterward the licenses of what the build contains: Lean's runtime and norm archive (Apache-2.0), Emscripten (MIT OR NCSA), musl, LLVM libc++, libc++abi, libunwind and compiler-rt, mimalloc, libuv, koffi and Lasm's presenter (MIT). Apps merge no copyleft code. licenses/<package>/ holds the license records of all Lake dependency compiled into program.wasm; alongside npm interop, node_modules/ holds all bundle alongside its own license. Keep these files whenever you allocate a dist/.
• Edge, browser, WASI, Fastly and wasi-http outputs get the identical notices, rewritten to say what their records contain, written automatically: a THIRD_PARTY_NOTICES.txt in all output directory, a abbreviated /*! … */ licence banner on the JavaScript a phase bundles (the border glue, the browser loader), the entire notices document inner the Wasm of server-side outputs (a lasm.notices custom section, so it travels alongside all deployment), the document in the Fastly package, and THIRD_PARTY_NOTICES.lasm.txt in Vite builds. What this method for your app: docs/LICENSING.md.
• Tool packages and publish archives. Each @lasm/… tool bundle has an SPDX license site and the archive's licence files. The exact sources of the (L)GPL pieces the Lean archives merge (GNU MP, the GNU C Library, GCC's runtime libraries, the Linux UAPI headers, MinGW-w64) and Lean's own origin are mirrored as resources of the publish that publishes them (lean-4.35.0-tiers-v2). Lasm ships no Git and no Apple SDK files.
• The Lean name and logos are trademarks of Lean FRO. Lasm is not affiliated with or endorsed by Lean FRO.

Herdr is a desktop app for terminals and coding agents. Keep activity in spaces, see which agents need you, and depart terminals operating whenever you near the window.

curl -fsSL https://releases.herdr.dev/app/install.sh | sh

Linux needs a desktop meeting and a operating Vulkan driver. macOS builds are accessible for Apple Silicon; Intel Mac users can build from source. Linux builds are x86-64 and ARM64.

The installer adds Herdr to your apps and puts the command in ~/.local/bin. Add that directory to your PATH if the installer asks. On macOS the app lives in ~/Applications/Herdr.app. For drag-and-drop facility on Apple Silicon, download Herdr.dmg and drag Herdr to Applications.

Run in PowerShell on x64 Windows alongside curl and tar installed (Windows 10 1803 or newer):

irm https://releases.herdr.dev/app/install.ps1 | iex

Herdr appears in the Start menu. The installer adds %LOCALAPPDATA%\Programs\herdr-app to your person PATH. Open a new terminal to choice it up.

Both installers download and run code. Read the shell installer or PowerShell installer archetypal if you prefer. They additionally instal herdr-core if it is missing. The app can assistance instal or update a center it cannot use.

A space holds activity on one machine, normally in one repo. Each area has tabs. Split a tab into panes to put terminals or mod panels beside all other.

An unnamed area follows its archetypal terminal's folder. Name a area or tab whenever you desire a tag that stays. New tabs commencement in the focused terminal's folder.

The agents sidebar brings agents from your spaces into one list, including workers started by another agent. Agents that study position display as:

• Working: motionless busy.
• Blocked: waiting for you.
• Done: completed during you were looking elsewhere.
• Idle: not working, or a completed delegate you have looked at.

Click an delegate to see it. A employee without a pane opens in peek, complete your tab. Keep it as a tab if you desire it beside your another work. Ctrl-click a live terminal location in terminal content to peek at it; use Cmd-click on macOS. An location specified as t7 method a terminal on the identical device as the terminal showing it. vps/t7 names one on another machine.

The opening arranges terminals. The center runs them. Closing the opening leaves them running; decision a pane or tab ends its terminals. After a reboot or center crash, kept panes get caller shells in their final folders, not their old programs.

Add an SSH device from Settings → Machines or the sidebar's Add device action. Pick a presenter from your SSH config or category how SSH reaches it. Spaces on that device run their terminals there, not on your computer.

Each device keeps its spaces, tabs and splits in its core. Connected screens portion that construction and the live terminals, but keep their own concentration and zoom. Remote activity keeps operating whenever your local opening closes or your laptop sleeps, as lengthy as the distant device and center remain up.

Open the command palette to discover an act by name, or open Settings to alter fonts, colors, appears and another preferences. The built-in layouts contain Herdr, Terminals and Herdr 98. A layout arranges the window. Mods are small JavaScript programs that diagram its panels, menus and dialogs.

Duplicate a shipped layout or mod before changing its construction or code. Your copies remain yours; Herdr updates the shipped ones on start. Save a individual layout, mod or key document and the opening reloads it. A damaged edit keeps the final fine type and reports the error.

Ctrl+Shift+P shows all command and its key (Cmd+Shift+P on macOS). Change any key in keys.json; see the keys section of the mod guide for the format.

Layouts and mods · Commands

Installed releases inspect for updates in the backdrop and download a new app beside the operating one. It takes complete whenever you discontinue and reopen, or choose the update action. Your terminals keep operating in the core. Settings → Updates shows what is available. What's New opens following an update; you can open it again from the command palette. Builds from origin do not update themselves.

Usage telemetry is on by default in releases. Turn it off in Settings → Privacy. Mods are trusted code, not sandboxed extensions. Read security and privacy before installing person else's mod.

This prints the delegate guide for driving the window. The herdr-core accomplishment points agents here. Use herdr-core for operating and coordinating programs; use the app to alter what you see.

herdr-app ls herdr-app status herdr-app commands

The archetypal two inspect the open window. The command catalog additionally plant without one. See the command reference for arguments.

For bugs, mod API requests and code contributions, see Contributing.

Clone this repo alongside its submodules. Use Rust 1.95.0 and Zig 0.16.0, the versions used in CI. Linux needs the betterment packages listed in that workflow.

git copy --recurse-submodules https://github.com/herdrdev/herdr-app.git cd herdr-app just build just test just install

Install just to use these recipes. The phase installer builds a publish and adds the app to your desktop. On Linux it links to this checkout, so keep the checkout in place. Quit and reopen Herdr to use the new build.

Documentation checks additionally need Bun: fair docs-check checks generated pages and CLI examples; fair docs-generate refreshes the citation pages.

To difference example changes on Windows, Linux or macOS, run the identical fixed workloads against all build:

python scripts/bench.py --bin <app executable> --set spinners --seconds 20

The runner requires hc on PATH and uses the Python executable operating the script. It prints a distinctive relic directory alongside the run settings, counters and results, afterward stops its personal app, terminals and core. Both sets use Python fixture programs; the default set’s TUI workload replaces historic btop measurements. --only spinners measures fair the quiescent native spinner scenario. Keep the opening apparent and the display awake, and difference the identical opening action and display settings; idle windows may diagram at a lesser rate. Windows records visibility, foreground action and display Hz at all measure boundary; another platforms grade these observations unavailable. Visibility does not established occlusion. Draws are opening render calls. Render-to-paint elapsed period stops before environment finalization, backend drawing, uploads and presentation; it is distinct from OS procedure CPU time. Neither measures bodily display or the FPS HUD’s derived MAX FPS.

python scripts/bench_compare.py ghostty --root <artifact folder> reuses a run’s counterfeit delegate for the macOS comparison. Benchmark checks: python -m unittest detect -s scripts -p test_bench.py.

Read next

Doomformer compiles entire figure neural networks into ZDoom maps and runs them in ViZDoom. Voodoo dolls (the copies of the player that DOOM spawns for additional player-1 starts) do the arithmetic, and field ray levels and aircraft heights clasp the sums. Python says all exposed value rear from the operating equivalent and compares it alongside a NumPy entire figure reference, tolerance 0. One value off by one and the run fails. It is slow: concerning 23,000 times slower than NumPy on a small MLP (engine time; 65,000 times alongside a timer about the entire call), and a handwritten numeral takes 163 seconds of real-time DOOM in one map at the default agenda and 8 seconds at --opt 3.

Install · Proof · How it works · Films · Docs

pip instal git+https://github.com/mottopanikeiku/doomformer # Python 3.11+, Linux or macOS doomformer hello # 2 s: a small MLP, all value checked doomformer diagram --digit 7 # 15 s: the marine walks a 7 and the flat says it

doomformer doctor checks ViZDoom, Freedoom and the display, builds ACC if it is absent, and compiles an ACS probe before reporting success. The archetypal build needs git, cmake, a C compiler and network admission to github.com. Linux uses energetic runtimes: glibc-static is not required. On Fedora: sudo dnf instal git cmake gcc gcc-c++ make. The Colab notebook needs no setup, but you diagram on a browser canvas and doomformer mnist --image feeds it to DOOM, alongside no marine.

Holding FIRE, the marine inks a 3×3 broom of flat cells under him. READ makes the flat compose the 784 pixels into the network, and 1,355 voodoo dolls in the identical map compute it. With --digit, Python stands in for you: it presses the marine's keys and USE once, afterward lone advances the clock and reads.

 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄████████████████ ████▀▀ ▀████▀ ▀▀▀ ▄███▀ ████ ███ ███ ███ ████ ███▀ ████ ▀███ DOOM reads: 7 (right) -- the winner's doll lit it on the 7-segment display EXACT: all 248 values DOOM computed [...] equal the NumPy entire figure citation (tolerance 0) READ pass: 273 equivalent tics = 8 s of real-time DOOM at 35 tics/s, 3 s partition [...] 

Abridged at [...]; docs/commands.md has the entire output. diagram builds its map alongside --opt 3, so a READ takes 273 equivalent tics; at --opt 0, the first schedule, it takes 5,705 (163 s of real-time DOOM). Without --digit the command opens a opening and you stroll and diagram yourself; DOOM afterward runs in genuine time.

The dolls compute 784 pixels → 64 hidden units → 45 pairwise mark comparisons → 10 win counts. Only the numeral that wins all nine of its comparisons gets a doll through, and the row that doll crosses starts the flat manuscript that lights the numeral on the display. Python says rear the 784 pixels, the hidden layer, all difference and the answer and checks all 248 values (119 values, all peruse alongside its negated twin, affirmative 10 outputs).

EXACT method DOOM equals the entire figure network. It says nothing concerning whether the numeral is right. On the archetypal 100 MNIST test digits DOOM says 99 correctly, and 966 of 1,000 sampled from all 10,000; all outcome is exact. The entire figure network scores 97.16 % on all 10,000 (the drift example scores 97.58 %). The 30 walked digits (0 to 9, three scripted stroke variants each) all peruse correctly and exact at --opt 3, and the network is additionally trained on that blow distribution: the first type of this demo, a 784-32-10 network trained on MNIST alone, says lone 41.08 % of specified strokes. Through genuine X key events a drawn 7 peruse exact at the default --opt 3; a 7 and a 1 were tried at --opt 0 alongside an before network. Details · film

doomformer museum build writes museum.wad, a map you can perform without Python. You stage on seven flat pads to light a numeral and media READ. 136 voodoo dolls compute a small hand-written network: all digit's mark counts the segments that concur alongside it, and the winner's doll lights the display. MUTATE rewires one association of that network inner the operating level: section a to numeral 7 goes from +1 to -1, by changing the specials of its two importance lines. The identical 7 afterward says as 1, and RESTORE puts it back. The HUD and a scoreboard show the ten scores following all READ, and a camera position shows numeral 7's sixth mark doll: it passes its entrance before MUTATE and stops in forefront of it after.

$ doomformer museum verify 7 pads abc w_7a +1 DOOM says 7 scores [4, 6, 3, 5, 4, 3, 2, 7, 3, 4] EXACT (148 values; 744 tics; [...]) 7 following MUTATE pads abc w_7a -1 DOOM says 1 scores [4, 6, 3, 5, 4, 3, 2, 5, 3, 4] EXACT (148 values; 744 tics; [...]) 7 following RESTORE pads abc w_7a +1 DOOM says 7 scores [4, 6, 3, 5, 4, 3, 2, 7, 3, 4] EXACT (148 values; 744 tics; [...]) 

Here Python plays: it presses the marine's keys and USE, and during all READ it lone reads, alongside guarded readouts. It compares all 148 values alongside the NumPy citation of the network as it is wired at that moment. Without operating DOOM, the fixed extractor additionally shows that the rewired map's netlist is the network alongside exactly that one importance changed. I have run the entire map lone in ViZDoom. Its self-test map says the digits 0 to 9, afterward the 7 following MUTATE and after RESTORE, without a player. On a GitHub runner it logs the exact values in GZDoom 4.14.2, LZDoom 3.88b, UZDoom 5.0.3 and ZDoom 2.8.1, and in Zandronum 3.2.1 lone whenever all field tag is below 32,768. Details

Python says field ray levels and flat and ceiling heights from the operating equivalent and compares all alongside an independent NumPy entire figure implementation of the identical network. The inspect is entire figure equality complete the runs that were made, and says nothing concerning inputs that were not run. The tests assault it: raising one importance row in a small compiled map from 5 to 6 must neglect by exactly +1 on exactly the inputs whose dolls cross that line, and a readout that echoes a value Python wrote must neglect (pytest tests/test_tamper.py, three tests, concerning 15 s).

Readback is guarded by default: before each page, Python poisons and checks its USER slots, afterward requires the page to substitute them. Dropping a leaf cannot silently reuse a repeated input's answer or the former page's values. guard=False is an definitive one-map historic opt-out. Guarded builds have new hashes (ACS and metadata, not geometry or arithmetic); the hash record explains the change.

doomformer fuzz --nets 40 compares all value of 40 random nets run in DOOM (306 passes, 0 mismatches, concerning 10 s with --workers 2; a planted compiler bug is found). fuzz --edge puts weights, biases and inputs at the range limits: 15,000 nets over ten caller seeds, at --opt 0, at --opt 3 and as tile maps, made 113,605 passes and compared 1,987,632 values with no mismatch (the range inspect refused 47,686 of the inputs it drew, concerning 30 %), 3,000 additional alongside the generator widened to aircraft starts near the limits below (22,682 passes) and 2,000 additional that additionally diagram starts from 15,000 to 16,000 (14,782 passes), all alongside no mismatch. Earlier campaigns ran 2,000 random MLPs (15,374 passes, 276,594 values), 300 spiking nets and 100 random transformers complete all 8 attention, norm and MLP variants (99 ran; one all-zero matrix is unsupported), following the scheduling fixes; 200 spiking --edge nets made 12,794 passes with no mismatch. fuzz --edge does not diagram transformers. CI fuzzes 60 nets with a fresh, printed kernel on all shove and a longer run all Monday. The fuzzer and autonomous runs established four faults in this repo's own maps: two scheduling bugs and two aircraft limits. A aircraft move that starts additional than 14,018 units from zero keeps its mover occupied for three tics and drops the next petition on that plane, and a aircraft that starts above 16,000 is exact on the archetypal continue and incorrect on afterward ones, so DOOM disagreed alongside the citation on nets that net.check had accepted. inspect and compile now refuse them: planes commencement inner [-15,000, 16,000] and move within ±14,018 (doomformer verify --plane-sweep, docs/verification.md).

doomformer verify runs all input category of a small MLP (the classes concur alongside all input on 20 of 20 nets, under an assumption stated in the identical page). df.coverage counts what is compared: on MNIST all 248 exposed values, which are 129 values the citation defines and 119 twins, and the figure falls whenever a readout name is dropped. The map does not expose the 903 staircase counts and 1,351 entrance comparisons of the identical net; they are checked through the sums they feed. doomformer verify --extract net.wad --net net.npz says the net rear out of a compiled map without starting DOOM and compares all weight, bias and threshold alongside the origin net: the shipped MNIST net (784-64-45-10-10) comes rear equal from its map solitary at --opt 0 to 3, and so do 484 of 490 random nets at --opt 0 (the another 6 are equal but interrupt the plane contract) and 199 of 199 at all of --opt 1 to 3. EQUAL covers the arithmetic netlist, the aircraft contract, the trigger and reiterate flags, the mover speeds, the reset manuscript and the readout pages; timing and geometry are printed as NOT CHECKED. A changed importance row shows as exactly that weight. Of 23,622 sole edits to a small map at --opt 0 the extractor detects 17,906, and the 98 undetected edits that were run in DOOM on 12 inputs were all exact. It shows what the map says; that DOOM runs the map as peruse is what the exactness checks test. A mutation harness changes one row of a compiled map: of the 1,004 sites run (of 5,578) 297 are killed, all weight, sign and mark classes among them. Of the 707 survivors 590 equivalent a regulation (a redundant scroller, a freeze row a onward pass never needs) that total controls support, and 117 are input gaps (walking floors that lone several inputs expose); none is proven equivalent. doomformer lint --fuzz compared the static schedule checker alongside DOOM on 5,397 maps: 0 false negatives. The method is translation validation (Pnueli, Siegel and Singerman, 1998): a test of all compile, not a evidence that the compiler is right.

Who does what:

• The dolls do all multiply-add, activation and comparison. ACS flat scripts location cells, move input gates, rewind the dolls, awareness the earth and copy results out. None of the network's arithmetic runs in ACS. The toolkit's df.Agent is the one exception: it takes its argmax in ACS (docs/agents.md).
• mnist: Python writes the 784 pixel ports and decides whenever the dolls have stopped; the dolls choice the digit.
• demo and ask: Python writes the token ids and decides whenever the dolls have stopped, samples all letter from the logits DOOM computed and, whenever a example is cut into multiple maps, copies integers from one equivalent to the next. demo --one-map is one map alongside no Python between layers; Python writes the tokens and samples the letter following each pass.
• draw and his brain is the level: Python lone advances the clock and runs readout scripts (in draw, from READ on). The flat supplies the inputs (the 784 pixels, the sensed tokens) and the dolls choice the numeral or the action.
• demo --one-map --loop: Python lone advances the clock and runs readout scripts. The dolls choice all letter and write it into the next position.
• The fly loop: Python lone advances the clock and runs readout scripts, following calibrating the stage duration on a separate game that it does write. The flat draws the input spikes and the output spikes blaze the drive lines.
• --opt 3 (the default of draw; elsewhere --opt 0, the first agenda alongside guarded readback): an ACS manuscript copies each layer's ray levels into the next layer's entrance heights. It adds and compares nothing, and the dolls motionless do the sums, thresholds, comparisons and the choice, but "no ACS between layers" holds at --opt 0 to 2 only.
• doomformer machine: the dolls run the program oppose and the registers. By default the loop, the rewind and the halt check are an ACS script, and a stored program is loaded by the presenter before the archetypal tic. With --clock dolls a loop doll and row specials restart, rewind and halt the level, and ACS lone says values and checks that the dolls have stopped (docs/machine.md).
• learn digits: Python writes the pixels and the tag of all example, advances the clock and reads; the dolls compute the scores, the argmax and the importance update (docs/learning.md).
• python -m demos.brainlevel --lesion-at N or --lesion-when near|ahead: the level's own clock closes the doors of the lesioned units before decision N, or the archetypal period the tokens it senses fulfill the condition; Python lone reads.

In the draw, his brain, loop, fly and device runs a wrap (ReadoutOnly) makes any another call raise, and the commands are counted: 58 in a headless diagram pass, 710 in the movie run of his brain, 154 in the lesion run, 0 others.

The maps use ZDoom's UDMF format and ACS, so they need ZDoom (here ViZDoom 1.3.2 alongside Freedoom assets), not the 1993 executable. net.quantization_report(x) measures how far an entire figure example is from the drift example it came from. EXACT does not.

docs/HOW_IT_WORKS.md maps all part of a network to a part of the map: a value to a collection of dolls, a importance to a line, an activation to a staircase, notice to a corridor of ceiling gates, ablation to a door.

The motor has keen edges and the compiler plant about them. A aircraft mover refuses a second petition on the identical plane for as lengthy as the archetypal is motionless moving, and the afterward one is lost. A teleport row cancels the lines a doll crossed earlier in that tic. A item additional than 32,767 units from a BSP node can be submitted under the incorrect sector, so all map fits 32,000 units. These are ZDoom 2.8.1 behaviours measured in ViZDoom 1.3.2. The 32,000-unit regulation is needed on Linux; on macOS arm64 the cover did not happen in the investigation maps (cause not investigated), and the regulation is kept everywhere. The exported probe maps and the hello brain additionally ran in inventory ZDoom 2.8.1 (53 of 53 rows match), Zandronum 3.2.1 (50 of 53: it cannot find field tags complete 32,767) and GZDoom 4.14.2, LZDoom and UZDoom (44 of 53: planes are doubles there and the UDMF parser refuses coordinates beyond ±32,768; the coordinate cover stays). The hello brain's logged values equal the NumPy reference in ZDoom, GZDoom, LZDoom and UZDoom, and in Zandronum formerly its tags are moved below 32,768. The doll-clock oppose machine (multiply 7 9, 464 steps, 235,567 tics) and a SUBLEQ add additionally ran in GZDoom, LZDoom and UZDoom alongside all step's pc and registers equal to the interpreter's log; ZDoom 2.8.1 and Zandronum (tags below 32,768) ran a 50-step multiply and the SUBLEQ add exactly, and stalled Zandronum alongside default tags at stage 1 (Other ports). doomformer facts re-runs 28 probes (55 cases) alongside PASS or FAIL per row (about 10 s), and Engine facts lists all finding alongside the investigation or test rearward it.

Computers inner DOOM maps be already. counter.wad (2006) is a 4-bit oppose built from voodoo dolls and conveyor belts, conway.wad runs Game of Life in a Boom map, and Danny Spencer's DOOM calculator is an adding machine. Doomformer adds a compiler from integer networks to ZDoom maps, a measured catalog of motor behaviours that interrupt exactness, and a tolerance-0 inspect against a NumPy reference. docs/related_work.md lists what was opened and what all admission shares and does not.

hello runs a 4-6-5-3 entire figure MLP, demo is a 1-layer transformer trained on 136 authoritative flat names cut into 38 tile maps, --nightmare is the 2-layer example (56,390 dolls), and ask is a 2-layer transformer trained on 189 DOOM facts. docs/commands.md has all command and type alongside example output: mnist --image and --tiles, demo --softmax, --model doomnames_modern, --one-map, --loop, --opt, fuzz, verify, lint, tune, facts, machine, learn.

Times are from an idle 16-core arm64 Linux device operating up to 8 games at once; hello and diagram use one game. With 2 games, demo took concerning 1 infinitesimal and demo --softmax concerning 3.5 minutes on a occupied machine, and ask took 20 minutes on 3 games.

• "Not in its training names" is a low bar: 29 of 30 unselected samples of the 2-layer example at heat 200 are new, and the default demo writes one of its 136 training names for 6 of 10 seeds (the output says which). The default kernel (20) is picked.
• DEMON CANYON, the name --nightmare wrote, is a hand-picked example (seed 2, heat 150; the figure of seeds tried before it is not recorded). The 2-layer example was trained on 11,341 of 12,934 cleaned flat names.
• ask gets 94.7 % of its training paraphrases correct and 35.4 % of new wordings of the identical facts. "what does iddqd do" is a training inquiry and answers GOD MODE. A inquiry exterior the 189 facts gets an answer that is exact and meaningless.

His brain is the level. A flat manuscript senses the nearest demon, 1,345 voodoo dolls of the marine run his policy transformer and choice the action, and the flat turns him and pulls the trigger. Python advances the clock and reads. 50 of 50 decisions exact (seed 4). A decision takes 4,338 equivalent tics (124 s of real-time DOOM); alongside --opt 3 the identical 50 decisions choice the identical 50 actions, all exact, in 774 tics (22 s) each. In that run his dolls rotate for 21 decisions while the archetypal demon is far away, archetypal choose FIRE at decision 22, and choose it five times in all; five demons die. The policy imitates a scripted aimbot that sees exact demon positions. The demons are icy during he thinks, and alongside them awake (--live, below) he is deceased following 5.5 s alongside 0 kills, which the arena nearly forces; the movie time-lapses the thinking. Film · code

Run the experiments from a copy (pip instal -e ., afterward python -m demos.<name>). demos/README.md lists all command, its period and what it prints:

• python -m demos.brainlevel: 5 decisions in concerning 4 min; --decisions 50 --seed 4 is the 50 of 50 run, concerning 31 min; with --opt 3 the 50 obtain concerning 5 min on a loaded machine.
• python -m demos.brainlevel --seed 2 --decisions 12 --opt 3 --lesion 'x0:0;L0.ao:7;L0.x1:7;L0.m:0;L0.x2:0' --lesion-at 3: from decision 3 the level's clock closes the doors of 5 units and the marine turns anywhere the fit brain fires; 12 of 12 decisions exact, concerning 2 min.
• python -m demos.brainlevel --live --lives 3: the demons remain awake during his dolls compute; the flat samples the sensor formerly per decision and the act lands 773 tics later. Over 90 lives (seeds 4, 5, 6, all decision exact) he makes 0 kills and is deceased following a median 191 tics (5.5 s), before his archetypal act lands; the identical arena icy gives 22 kills a life. In this arena he cannot move and the archetypal demon damage arrives following a median 128 tics, so any performer that waits 773 tics dies first: a Python copy of the identical guideline alongside the identical postpone additionally makes 0 kills, and alongside a 3-tic delay 3.3. The informative part is the clear (python -m demos.brainlive sweep): alongside a caller act all 4 tics he keeps 79 % of the icy kills on 3-tic-old sensing, 36 % at 6 tics and 19 % at 12 tics.
• python -m demos.aimlearn: 2 lives in concerning 3 min; --lives 5 --seed 4 takes concerning 11 min.
• python -m demos.flyloop: 40 steps in concerning 3 min; --steps 900 runs to the end at stage 169, concerning 13 min.
• python -m demos.lobotomy: the lesion scan and 3 decisions in DOOM, concerning 1.5 min.

A transformer names a level. The 2-layer name example writes DEMON CANYON in 1,690 tile runs; a Python generator builds the level. One hand-picked example (seed 2). Not a corpus name.	A marine plays the flat it named. A 1-layer guideline on 55 games walks that level: doors, two kills, exit. 102 decisions, all exact. Python gives the compass and enemy positions. Seed 118 of 120, picked.
A perceptron learns inner one game. 38 ceiling-height weights, updated by dolls from an aimbot's labels. The current code gives 4, 22, 15, 20 and 16 kills complete 5 lives, 815 of 815 decisions exact. The movie is an before run on an older map layout: 4, 24, 26, 22, 24 kills, 931/931 exact, kernel 4. Python bins features and gives labels.	Lesions. A 7-pellet shotgun blast closes 7 neurons as doors and the marine stops firing: 0 kills complete 74 decisions, all exact. Picked from 3,000 random blasts, 4 of which were pacifists: 64 of the 11,440 seven-subsets of the 16 `x0` units are, and 5 neurons is the minimum.
A fruit-fly circuit. 255 neurons derived from the FlyWire connectome run the marine's lunge, grooming twitch and takeoff; refuse is silence. 169/169 steps exact. Simplified entire figure dynamics, synthetic input spikes, firing rates 0.6 to 2.7 times the drift model's, one seed.	A transformer in one map. No Python between layers: 3,548 dolls compose SHIL, 2,680/2,680 exposed values exact. A 1-layer, d=8 model. Python samples the letter. Time-lapse.
Generation without Python. The winner's doll sets the next token and the flat rewinds itself; Python lone advances the clock and reads. It wrote DAN in 5 passes (5,875 dolls). One example and the default prompt; the movie time-lapses the thinking. ViZDoom lists at most 4,096 objects, so 1,779 dolls are not drawn ([engine limit](docs/engine_limits.md#object-list-vizdoom-lists-at-most-4096-objects)).	A 4-layer transformer. It writes UNHOLY STRONGHOLD complete 10,166 tile instances and 1.9 myriad equivalent tics. Instances run on a pond of games, not 10,166 games at once.

The showreel covers all of them. docs/DEMOS.md has the numbers, the range of all inspect and the catalog of picked seeds, and docs/FLY.md covers the fly.

Compile a network into a map and let its outputs open doors, flash lights or shove the marine. This runs as pasted:

import numpy as np import doomformer as df # 2 inputs -> [a AND b, a OR b] -> 2 outputs, all integers net = df.MLP( weights=[np.array([[1, 1], [1, 1]]), np.array([[1, 0], [0, 1]])], biases=[np.array([-1, 0]), np.array([0, 0])], thresholds=[np.array([1]), np.array([1])], signed_input=False, ) with df.compile(net) as brain: for x in ([0, 0], [1, 0], [1, 1]): # computed by voodoo dolls; raises df.MismatchError on any difference from net.reference print(x, "->", brain(np.array(x)).tolist()) brain.record([np.array([0, 1]), np.array([1, 1])], "dolls.gif") # movie the dolls doing it

df.MLP.from_torch quantises a PyTorch example (example 02), and the earth and actions hooks put rooms in the map and nexus doors, lights and thrusts to the outputs (example 03). The identical API takes spiking networks, transformers, Conv1d and Conv2d, and learners that update their weights inner the map; mode="tiles" spreads a example complete a pond of games (doomformer scheme tells you which case you have). The guide is docs/BUILD_YOUR_OWN.md, and there are twelve one-file examples. Built item odd? Show and tell.

One map is one game, and one equivalent uses one core. df.run_many gives all input to the next idle game, checks all pass and returns the outputs in order, on your device or on a Ray collection you start. Nothing is hosted. 1,000 MNIST test digits in 14 games on one 16-core device took 2 hours: 966 peruse correctly, all 1,000 exact, 5,696,000 equivalent tics or 45 hours of real-time DOOM (models/mnist/doom_1000.json).

Tiles are the multi-map design: four tile maps, one per layer, in inhabitant games, alongside Python copying the tier values from one equivalent to the next. doomformer mnist --tiles --all --workers 6 peruse all 10,000 test digits in 1,390 s: 10,000 of 10,000 exact (248 values each), 9,716 correct (97.16 %), DOOM's one-hot equal to NumPy's on all digit (models/mnist/doom_tiles_10000.json). A numeral takes 216 equivalent tics and 0.83 s there against 5,696 tics and concerning 104 s in one map. doomformer scheme predicts seconds (rms error 13 % for one map and 22 % for tiles on 11 held-out K3 and K8 nets; on nets of another K the measured seconds were 0 to 40 % complete the prediction, and 21 % complete for MNIST at --opt 0), prints equivalent tics alongside an error collection (276 ± 7.2 % for MNIST at --opt 3, 272 measured) and recommends one. doomformer place tiles says MNIST at 81 digits per infinitesimal alongside 1 employee and 880 alongside 16 (steady state; 79 and 552 alongside equivalent start), all continue exact, at 0.72 s of motor CPU per numeral alongside 1 employee and 0.92 s alongside 16 (100 shipped digits, twice; 16 cores).

doomformer mnist --tiles --all --workers 6 # all 10,000 digits as tile maps, concerning 23 min pip instal "doomformer[ray]" ray commencement --head # another machines: ray commencement --address=HEAD:6379 doomformer mnist --all --ray --record mnist.json # all 10,000 digits, one map each, on a cluster

Budget one center and concerning 1.3 GB of RAM per equivalent (measured highest 1.24 GB). docs/scaling.md has the measurements.

• Schedules. --opt 1, 2 and 3 (df.compile(net, opt=N)) shorten the one-map schedule: doomnames_onemap goes from 3,488 equivalent tics to 1,512, 1,128 and 544, MNIST from 5,696 to 272 at --opt 3 (100 of 100 exact and 99 correct with the final constants, 300 of 300 before the final retune), and a DrawPad READ from 5,705 to 273 (30 of 30 walked digits right and exact). --opt 2 on MNIST ran on 76 digits (3,560 tics). The ACS copy at --opt 3 is under "Who does what". doomformer lint WAD flags aircraft moves that can portion a tic (0 false negatives on 5,397 fuzzed maps of the compiler as shipped; alongside an old barrier-height bug restored it caught 65 of 67 failing maps, and 66 of 66 on the identical nets following its model learned the first-tic halt that it had missed), doomformer lint --net MODEL additionally checks the aircraft bound, and doomformer tune measures the timing edges (docs/scheduling.md).
• A oppose device and two stored-program machines. doomformer device multiply 7 9 is a ROM oppose device (the program is the map's geometry): it prints 63 following 464 steps (39 dolls), the program oppose and all enroll checked at each step; fib 20, gcd, primes and pow2 40 run too. --clock dolls takes the ACS iteration manuscript out (a iteration doll and row specials restart and rewind the level) and --blind says lone formerly at the end. doomformer device subleq all runs a SUBLEQ device alongside 18 recollection cells of -64 to 63, operands as addresses and programs that rewrite their own instructions: add, 7 × 9 = 63 and a self-modifying sum run on one map (one sha256), 1,624 equivalent tics a step, all step compared alongside a Python translator at tolerance 0. Changing one row of the ROM or the decode makes the run diverge at the predicted step. A program that writes the three cells of the education it is executing sets a infringement latch in the map, which halts the flat at that stage (--latch; all 28 of 400 random programs that do so were flagged at the interpreter's step); without it the map computes a incorrect value there. A 103-step iteration runs exact on the two clocks, and a bubble kind does not fit in 18 cells. Memory and registers are bounded aircraft heights, so these are finite-state machines and no assertion that DOOM is Turing complete; plain SUBLEQ is worldwide alongside unbounded memory, and no universality argument is stated for this restricted form (docs/machine.md). demo --one-map --loop --until-eos lets the end-of-text victor halt the loop.
• A learner that starts blank. doomformer study digits --steps 1500: a 10-class perceptron alongside 370 weights, all 0, learns 8×8 digits inner one map. The weights are ceiling heights; the dolls compute the scores, the argmax and the update, and Python writes all example's pixels and label. After all of the 1,500 steps all 455 exposed values, every weight included, equal a NumPy twin at tolerance 0 (about 80 min on a loaded machine). Held-out accuracy goes from 10 % to 71.2 % on 500 digits; a textbook perceptron without the importance clamp reaches 81.0 % on the identical stream. On 20 NumPy streams (seeds 0 to 19, one of them the DOOM stream) the clamped twin averages 74.8 % ± 5.3. The onward corridor has 6 gates, so a mark lone sees weights in [-3, 3] and larger ones keep moving unseen; that expenses concerning 10 points on this stream and 3.6 on average. The update regulation and the labels are Python's (docs/learning.md).
• Quantisation. df.MLP.from_torch(model, calib_x, levels=4, calibrate="mse") additionally folds BatchNorm, lowers AvgPool and MaxPool (MaxPool by comparisons, exact on the staircase counts) and takes GELU and SiLU as staircases; df.qat.fit adds quantisation-aware fine-tuning. On 8×8 digits at 4 levels a depth-6 MLP goes from 88.9 % alongside max calibration to 93.7 % with MSE calibration (float 95.9 %) and a CNN from 92.7 % to 95.1 % (mean of 3 seeds, models/quant/EVAL.md); QAT is no improved than MSE calibration on ReLU Linear and Conv nets, and onward on nets alongside multiple max pools or GELU (BatchNorm + 2 MaxPool CNN: +4.6 points at 2 levels, +0.5 at 4). The lowered nets ran exact in DOOM on 5 digits each. df.Transformer.from_torch lowers a torch_models.GPT trained alongside the staircase recipe: a 24k-parameter level-name model is 5.6 % worse in perplexity than its drift phase (7.75 against 7.34), ran exact in DOOM on 3 held-out names, and is behind a 5-gram baseline (5.84). On a second corpus (Python citation prose, windows absent from training, one seed) it is 6 % rearward its drift stage, 17 % rearward a plain drift GPT alongside the identical steps and 34 % rearward its 5-gram. It does not convert a transformer trained elsewhere.
• A example that learned an algorithm. models/induction, a 2-layer entire figure transformer, is trained on induction over random tokens, which no figure array can solve. Held-out accuracy is 0.9995 against 0.9991 for a drift GPT of the same size, 0.069 for a bigram array and 0.233 for a 4-gram table; on pairs never seen in training it is 0.9995 against 0.000 for the tables. python -m demos.induction --heldout 25 runs 25 sequences in DOOM: 25 of 25 exact, 520,749 values. One kernel per row, and a d=16 ReLU K=4 run unsuccessful to study (log kept).
• Interventions. intref.forward(interventions=...) and DOOM runs place a value (zero, set, mean, resample, scale, add or eliminate a direction) at a site, stance and head, and all value is compared alongside the likewise patched reference: 24 of 24 activation-patching rows of doomplayer and 40 of 40 patched runs of the induction example (10 pairs per kind) ran exact in DOOM. In tile manner Python says all pre-activation the dolls computed and writes the patched value into the next tile's ports, and the dolls compute everything downstream; exactness does not inspect that the place value was the right one. Patching recovers the planted caput of a hand-built 1-layer model, (b + c) mod 4, alongside 0 disagreements over 384 pairs; alongside a backup caput sole patches divided 0.5 and 0.5 and two circuits remain, and alongside a caput that lowers the logit difference in several contexts the proportion of method hides it, so the circuit hunt reports per-context accord too (OR and AND redundancy appearance the identical to single-cell patching). Rows that place the entire residual or a entire location at the read stance are flagged and remaining out of the header numbers. Steering doomplayer alongside a investigation direction changes 39 of 86 contexts; it strikes random, span-of-the-data and random-context directions, and does not attack a shuffled-label probe (where the shuffle has adequate distinct directions) or a 'fire vs not fire' probe. "No compact circuit" in the induction model holds for average ablation at all position; alongside the corrupt run as baseline 4 of 6 components reconstruct 0.991 on answer pairs. The lesion data corrected the demos above: DEMON DEATH is not a selective lesion, since 355 of the 416 single neurons alter that example (docs/interventions.md).

• DOOM is slow. Engine period of one continue against the NumPy citation (14 to 48 µs) is concerning 23,000 times for a 12→16→6 MLP, 1.5 myriad times for MNIST in one map (73.2 s of motor CPU), 60,000 times for it at --opt 3 (2.84 s) and about 15,000 times for MNIST in tiles (docs/scaling.md). A one-map continue expenses what the idle map costs: the conveyor scrollers are the entire 2.84 s of MNIST at --opt 3 (doomformer place idle). Fewer scrollers do not help: with half of them the equivalent tics twice and a continue expenses 1.8 times more, and alongside one per field the continue is wrong (doomformer place stack), so 0.5 s per continue needs an motor change. With a timer about the entire call (write inputs, run, peruse back) the 12→16→6 MLP is 726 ms against 11.1 µs, concerning 65,000 times (30 runs, Speed), and a fly-circuit stage is concerning 73,000 times.
• Attention is entire figure attention: ReLU-style in most models, softmax computed by the dolls in three. No example has LayerNorm (doomnames_modern has an entire figure RMSNorm), and none is a drop-in drift transformer. Transformers are trained offline in PyTorch alongside quantisation-aware training (training/); MLP.from_torch converts MLPs and CNNs, and Transformer.from_torch lone the torch_models.GPT component trained alongside that recipe.
• The compiler is validated in ViZDoom 1.3.2. The investigation maps, the hello brain and the doll-clock oppose device ran in other engines (stock ZDoom, Zandronum, GZDoom, LZDoom, UZDoom); no network larger than hello did, and in the GZDoom family aircraft arithmetic differs, so the aircraft limits of this repo are ZDoom's. The compiler emits field tags complete 32,767, which Zandronum cannot find.
• The checks shield the nets and inputs that were run. The fuzzers do not shield learning maps, additional than 4,096 objects, or transformers in tile manner (Not covered).
• --one-map runs a smaller example than demo (1 layer, d=8, 6 positions), since the 136-name example needs 116,968 dolls and does not fit one map.
• The marine's policies imitate a scripted aimbot that sees exact positions. Python bins them into 86 imaginable observations and supplies the labels. There is no reward-driven RL and no learning from pixels.
• Showcased seeds, lesions and names are picked. Seeds and selection lists all pick.

Code and docs: MIT. Data keeps its own licence (THIRD_PARTY.md): the level-name lists are Doom Wiki (CC BY-SA 4.0) and id Software's origin (GPL-2.0), the 100 example MNIST digits are CC BY-SA 3.0, and the fruit-fly circuits in models/fly are derived from the FlyWire connectome (CC BY-NC 4.0, non-commercial). Freedoom graphics are BSD-licensed. DOOM is a trademark of id Software / ZeniMax; this project is not affiliated alongside them.

Ashley Graham is a example and entrepreneur who has spent her occupation challenging who is seen, heard, and marketed to, transforming that power into a expanding business.

Ten years following her "Sports Illustrated" cover, Graham took the phase at Business Insider's The Long Play to unpack how she has built a individual brand throughout fashion, beauty, entertainment, and person products without losing what's at the center of her identity.

Graham said concerning Lucci, her new project in the vino business, and her longtime alliance alongside JCPenney during her discussion alongside Business Insider's administrator editor, Leena Rao.

During the conversation, titled "Breaking the Mold," Graham additionally stated that getting many of rejection first on in her occupation has made her into a improved businessperson.

"If it's not for you, there's another item for you. And you can't obtain it personally," Graham told Rao.

Read next

Overview

GLM 5.3, a extensively accessible open-weight example released by Z.ai in August, can acknowledge and utilize vulnerabilities in latest versions of the Mozilla Firefox browser using safety fixes that have been published but not yet shipped to users. The opening between a fix being published and reaching users is known as the patch gap.

In our experiments, GLM 5.3 used this gap to build a webpage that, whenever visited by a Firefox user, peruse a document from the visitor’s device and sent it to the attacker alongside no additional person interaction. In particular, we established that any Firefox type released between September 17 and October 26 could be compromised in this way using lone data accessible at the period of release.

The place gap is a known weakness in application publish practices, and it exists extensively throughout software, e.g., browsers, phone functioning systems, and router firmware. Exploiting it earlier required important period and expertise, or particular admission to frontier models alongside advanced cyber capabilities, so few attackers could mark these vulnerabilities before they were fixed.

Our chief finding is that extensively accessible open-weight models can now do much, or equal all, of this activity on their own. We deliberately designed our setup to emulate what a comparatively unsophisticated performer alongside constricted resources could achieve, using lone data accessible at the period of all version’s release. Once set up, it disbursal lone concerning $1,000 to successfully assault all Firefox version.

In all of our compromises of latest Firefox releases, GLM 5.3 additionally established and used an unpublished exposure in conjunction alongside those established via the place gap. We contacted the Mozilla squad to disclose our findings and conversation ways to mitigate these attacks. Mozilla has since shipped a new type of Firefox (159.0, released on October 27, 2026) that patches the earlier undisclosed vulnerability, which should create it additional difficult for GLM 5.3 to colony Firefox via patch-gap exploits.

Open-source projects are particularly susceptible to this benevolent of assault as their code is publically available, but we doubtful any application project anywhere a example can discover the satisfied of upcoming safety changes before publish is vulnerable, including closed-source projects.¹ We anticipate this danger vector volition worsen as open-weight cyber capabilities continue to improve.

Further findings from our experiments on Firefox:

• GLM 5.3 exploited the place gap notwithstanding existing countermeasures. To dilatory downward would-be attackers, published safety fixes are obfuscated as average improvements and do not disclose particulars of underlying vulnerabilities. GLM 5.3 was capable to peruse the code and decide which changes connected to safety patches.
• The category of utilize we demonstrated can be extremely serious. We used GLM 5.3 to create a website that, merely whenever visited by a Firefox person and without additional interaction, gave the attacker the capability to exfiltrate records from the user’s computer. Firefox has complete 200 myriad energetic users, and this utilize could be used to peruse their passwords stored in the browser, pilfer authentication cookies, or perspective another personal data on the user’s computer.
• We did not trigger any safeguards or refusals from any provider, including Z.ai, whenever using GLM 5.3 in this way. We framed the project as a safety exercise, but our actions were alternatively indistinguishable from those of a genuine attacker.
• Similar attacks on Google Chrome have not succeeded as of the period of writing. We do not obtain this as powerful evidence that attacks could not win alongside additional advanced elicitation or by using additional capable open-weight models (potentially including the lately announced Kimi K3.1 Pro).

Background

In April 2026, Anthropic’s notice of Claude Mythos Preview marked a leap in AI cybersecurity capabilities. Since then, it has been apparent that frontier AI models are capable of detecting vulnerabilities and crafting complex exploits in genuine manufacturing software. Anthropic lately demonstrated this by giving examples of how an inner example was capable to discover and utilize crucial vulnerabilities in extensively used software.

Frontier AI labs have responded by giving several defenders first admission to advanced capabilities (via projects akin Glasswing and Daybreak) and heavily restricting broader access. This scheme is meant to authorize defenders to acknowledge and place vulnerabilities before attackers can utilize them. However, a gap frequently exists between a exposure fix becoming community and it being deployed to all the users of the applicable software. This patch gap exists in two places: fixes becoming community before they are released to users, and users continuing to run old application following an update. In our research, we concentration on the gap between fixes becoming community and their broad release.

Beta versions of software, which developers use to test code and discover newly introduced bugs, are one scheme by which exposure fixes rotate into community before they are mostly released. Betas typically have a smaller person basis than community releases, made up of users consenting to test newer and possibly unstable features. For open-source projects, data is equal additional broadly available, as the complete codebase is community and upcoming changes are typically viewable in beta or “nightly” code branches.

The place gap is a known safety issue, but the period and ability historically required to utilize it have constricted how many actors can do so (and the naturally constricted life of exploits developed in this way method attackers may choose to expend their notice elsewhere). Advancing AI cyber capabilities have changed this calculus.

Although unrestricted admission (without cyber guardrails) to the most capable frontier models is tightly controlled, open-weight models are broadly accessible to anyone without restriction.² This open admission can advantage cyber defenders by enabling preemptive exposure finding and event response, particularly for defenders without admission to restricted frontier models. While we concentration current on an insulting capability, we do not create claims on how open-weight models volition effect the balance between infringement and defense.

Open-weight models have historically been unable to reliably utilize the place gap, but their capabilities are steadily improving. To see whether that limitation motionless holds, we tested whether GLM 5.3, a extensively accessible open-weight example released in August 2026, could use the place gap to colony the most latest releases of Firefox, a web browser alongside complete 200 myriad energetic users.

Methodology

We tasked GLM 5.3 alongside creating a webpage that, whenever visited by a Firefox user, says a local document on their system.³ This can be used to peruse the user’s personal documents, copy passwords stored in Firefox, and pilfer authentication cookies, allowing the attacker to log into several online services as the user. We chose this mark since it reflects an assault serious adequate to logic genuine damage to users.

We provided the example alongside the particular Firefox type on the user’s device and several essential tools, afterward let it continue operating until it developed a prosperous exploit. To evade impacting third parties, we did not provision the example net access; instead, we immediately provided the publically accessible data we idea it would apt need. We provided lone data accessible at the period of the mark versions’ release, so the example could not use data concerning vulnerabilities discovered later.

We designed the surroundings to approximately approximate what an attacker alongside minimal specialized cognition and norm betterment tools could elicit from the example if they let it run online. We accessed GLM 5.3 through the two its first-party API and third-party APIs, framing the project as a safety exercise. Despite our actions being indistinguishable from those of person attempting to mark genuine users, at no item was our example use restricted, and we encountered no refusals.

Beyond essential instructions to mark the place gap (i.e., inspect bug fixes not yet unified into the stable release), we let the example run autonomously alongside no person input. The example identified upcoming safety fixes, selected vulnerabilities, and built a complex utilize sequence on its own.

Results

GLM 5.3 successfully developed attacks against all six Firefox releases between September 17 and October 26,⁴ using lone data accessible at the period of all version’s release. Visiting the webpage built by the example caused the browser to peruse a local document and dispatch its contents to the attacker’s server without additional person action.⁵

The attacks took significant attempt for the example to develop. In one attempt, GLM 5.3 used an upcoming Firefox fix to acknowledge a recollection safety flaw, afterward developed a way to peruse and modify recollection inner the browser, but Firefox’s safety protections motionless prevented the example from study the mark file. The model’s final assault composed the first utilize alongside multiple additional stages to circumvent the remaining layers of security. The example diagnosed crashes, abandoned unsuccessful approaches, and iterated its method until merely visiting the website was adequate to admission the file. We gave GLM 5.3 up to 48 hours to discover an exploit, but its fastest attempt needed lone 12 hours.

In supplement to vulnerabilities discovered through the place gap, our attacks on the most latest Firefox versions additionally relied on an unpublished exposure that the example rediscovered on all attempt. This allowed it to leverage constricted authority of the browser into the capability to peruse records from the computer.⁶ We shared this exposure alongside Mozilla, and it is now patched as of the October 27 Firefox 159.0 release. We have not yet confirmed whether akin attacks can win on 159.0 stated this patch, but doubtful it should create things at smallest substantially additional difficult.

Our total investigation expend targeting Firefox exceeded $100,000 in API costs, including experimentation to build a realistic offline surroundings and our preliminary testing. However, formerly we developed our harness and pointed GLM 5.3 in the correct direction, exploiting the browser became cheap and reliable. Our marginal disbursal of compromising a new type of Firefox was concerning $1,000 at API pricing, and would possibly have been lesser if using subscription accounts.

An attacker unconcerned alongside the risks of letting an autonomous delegate create an utilize alongside net admission could replicate our setup much additional cheaply and effortlessly by giving the example unrestricted net admission alternatively of going through the attempt of operating it offline in a sandbox.

After we discovered GLM 5.3’s capability to colony Firefox, we decided to measure whether a akin setup could colony Google Chrome. We used the identical harness and techniques and, as of the period of writing, have not been capable to create an equal exploit, notwithstanding spending concerning $100,000 in API expenses on attempts.

Kimi K3.1 Pro was released via first-party API admission on October 23, alongside the weights planned to be released in first November. Kimi K3.1 Pro has not been part of our experiments, but limited benchmark data suggests it may outperform GLM 5.3 on insulting cyber tasks. We scheme on evaluation additional advanced open models on a wider assortment of application in the future.

Implications for another software

The conditions needed for patch-gap attacks are average throughout the application industry. Whenever a safety fix becomes apparent before it reaches users, an attacker has the chance to reverse engineer it into an exploit. In September 2026, we saw patch-gap exploits targeting Chrome. In the identical month, a vendor published patched builds of PHP additional than six hours onward of the coordinated publish of patches for two crucial vulnerabilities. These first patches could have contributed to thousands of utilize attempts before the community release (which afterward climbed to millions immediately afterward).

While Firefox and Chromium are open source, the place gap additionally poses risks to closed-source software. Anthropic demonstrated that Mythos is capable of exploiting the place gap on Windows without any of the project’s code publically available. We did not explicitly test the capability of GLM 5.3 to utilize the place gap on closed-source projects, but as open-weight cyber capabilities continue to improve, it volition plausibly be imaginable soon, if it is not already. We are particularly concerned concerning application that users update small frequently, akin router firmware or phone functioning systems, since general colony can have grave consequences and most users have a much longer opening of vulnerability.

Addressing this danger volition apt necessitate reducing the period that exposure fixes remain community before being unified into the broad release. We created exploits inside two days, but another attackers could be faster. Merely providing defenders admission to stronger closed models does not resolve the underlying structural issue; a community fix, despite of how it is found, inherently flags anywhere vulnerabilities are. Defenders have a few levers to drag to mitigate these attacks, specified as keeping safety fixes personal until they are prepared to container or shipping them from beta to publish additional quickly. Both Firefox and Google Chrome have begun shipping updates all week. Regardless of the approach, it have to be assumed that formerly a exposure fix is in published code, attackers can and volition use it to mark the current release. Defenders should evade patching multiple vulnerabilities simultaneously if they can be chained together.

Conclusion

GLM 5.3 compromised six of the most latest Firefox releases by exploiting the place gap. We used a deliberately essential setup, and notwithstanding this, the example reliably built prosperous exploits without individual input, at a marginal disbursal of approximately a thousand dollars per Firefox type compromised. These attacks relied on a key non-public exposure that has since been patched, and we were not capable to accomplish akin outcomes on Chrome (but we do not think this rules out akin attacks succeeding alongside improved elicitation or stronger open-weight models).

We see these results as evidence of the diffusion of advanced cyber capabilities; many another pieces of application are apt already susceptible to akin patch-gap attacks, and we anticipate the figure to addition as additional capable open-weight models are released.

Read next

Reddit CEO Steve Huffman stated in an earnings call today that Google’s AI-powered hunt modes do not assistance alongside traffic to the platform, echoing problems facing other websites and publishers. As part of its Q3 2026 earnings, Reddit revealed that hunt traffic in October has “dropped by additional than 1 myriad referrals on average per week,” and he attributes part of the company’s struggles alongside Google traffic to how AI Mode and AI Overviews alter the hunt experience.

“The actuality is, AI Mode does not run traffic,” Huffman says. “Not for us, and not to anybody, as far as I know. That’s fair a essential change in how Google works. It used to be a traffic driver, now it’s not.”

He says that AI Overviews and AI Mode have “evolved a lot” and now, at a “minimum,” shove “everyone downward the hunt page.” Huffman additionally says that Reddit believes its satisfied that’s machine-translated into another languages is being classified lesser in hunt results, which he says would chiefly power the business exterior the US.

However, Reddit is motionless a “top hunt term in Google,” Huffman says. “This doesn’t say item concerning the net consumers’ petition for Reddit. People motionless desire Reddit. It says Google is not sending them to Reddit the way they used to.” He additionally says that Google is “crawling us as difficult as ever, so the petition hasn’t changed from their item of view, either.”

(Google’s endeavor has been affected by AI Mode, too: it said yesterday that it’s seeing “lower monetization” in AI Mode ads, although it’s now bringing AI ads to additional countries.)

To try and combat the hunt referral difficulties, Reddit is operating to create the phase a “direct, sticky, regular destination.” Yesterday, it introduced a “For You” feed alongside recommendations connected to your interests, and in August, it started evaluation an test that uses AI to rotate posts into abbreviated videos.

Reddit additionally announced today that it’s going to force everyone to log in, which Huffman claims volition be “better for person experience, improved for our ads business, is additional in row alongside safety regulations, and additional protective of Reddit data.”

The Adventures of Tom Sawyer marks its 150th commemoration this year. It was archetypal published in 1876, the centennial twelvemonth of the American Founding. The novel itself marked its own benevolent of founding instant for American literature, which had been laboring—to get a expression from The Federalist—under the “arrogant pretensions of the European.” America may have damaged liberated of Great Britain in 1776, but we remained enthralled to Europe culturally for much longer. In his 1837 composition “The American Scholar,” Ralph Waldo Emerson lamented that American writers had “listened too lengthy to the courtly muses of Europe” and scraped by on the “sere remains of abroad harvests.”

Emerson afterward issued what Oliver Wendell Holmes, Sr. dubbed an “Intellectual Declaration of Independence.” For Emerson, “genius looks forward.” He wanted to find, as he put it in his 1844 composition “The Poet,” the Homer of America—a bard “with a tyrannous eye” who “knew the value of our incomparable materials, and saw, in the barbarism and materialism of the times, another carnival of the identical gods whose image [one] so much admires in Homer.” In much the identical spirit, Walt Whitman longed for a “democratic literature” filled alongside “archetypal poems” that could thicken America’s traditional “marrow.”

American men of alphabet specified as James Fenimore Cooper, Edgar Allan Poe, Nathaniel Hawthorne, Herman Melville, and Henry Wadsworth Longfellow all made their contributions in the battle to drag distant culturally from Europe. But it was Samuel Clemens—Mark Twain—who made the decisive revolutionary break. In the words of the reviewer William Dean Howells, “I knew them all…our sages, poets, seers, critics, humorists; they were akin one another and akin another written men; but Clemens was sole, incomparable, the Lincoln of our literature.”

With The Adventures of Tom Sawyer, his archetypal novel, Twain offered a new first champion for democracy. He replaced the squeaky-clean “model boys” that tended to celebrity in mid-19th hundred years serials akin McGuffey’s Eclectic Readers and Peter Parley’s Magazine, to which Twain’s begetter had subscribed. Tom is an altogether additional vivid, additional completely realized benevolent of boy. He leaps off the leaf from the extremely archetypal term of the novel, which is his name, printed in huge chief letters: “‘TOM!’” yells his Aunt Polly. “‘What’s gone alongside that boy, I wonder? You, TOM!” An first assessment from England criticized the “queer Americanizing of the language.”

The frontier vernacular was part of the point, however, as distinctive as the behavior of the boy hero. In the archetypal chapter, on day one alone, Tom hides in a closet gorging on forbidden jam, runs distant from Aunt Polly’s whipping, plays hooky from academy to go swimming, opportunistically steals sugar at the meal table, lies to his aunt concerning being in school, and gets into a combat alongside a new boy in town since he is well-dressed and wearing shoes. Twain announces outright that Tom “was not the Model Boy of the village.” He reinforces this theme so fine throughout the novel that the Brooklyn Public Library excluded The Adventures of Tom Sawyer from their study area upon its publication.

Other reactions were additional appreciative and far-seeing. Moncure Conway, Twain’s companion and written delegate in London, observed: “The publish volition no doubt be a favorite alongside boys, for whom it must in fine part have been intended; but next to boys we should say that it power be most prized by philosophers and poets!” Conway was among the few (even to this day) to grasp the deeper import of the novel, which is frequently wrongfully dismissed as merely a humorously nostalgic narrative for children. But one philosopher who seems to have appreciated Tom Sawyer’s many subtleties was Friedrich Nietzsche. He wrote to his companion Franz Overbeck in 1879 that his mother had been study it to him so he could remainder his strained eyes. In another letter, this one to the novelist Paul Rée, he declared that he preferred Mark Twain’s American “silliness” to German “cleverness.”

The Mischief-Maker of Missouri

Perhaps there is a Nietzschean streak to Tom. He certainly delights in upending the staid morality of St. Petersburg, Missouri, whose inhabitants Twain describes as “grave, unromantic men.” They are locked into the drab ritual formalities of what Leo Strauss called the joyless chase of joy: grinding labor without much pleasance in profit; dutiful rote piety without genuine religious passion. Tom shocks and offends the sensibilities of nearly everyone about him, but he additionally enlivens their earth and broadens their horizons, turning the dour solemnities of the town into a backdrop for his playfully mischievous imagination. The most celebrated environment in the publish is the one in which Aunt Polly punishes Tom for playing hooky by making him whitewash her barrier on a Saturday morning. In delayed edits, Twain enhanced the barrier from four feet elevated to mythic proportions—a forbidding construction nine feet lofty and 30 yards wide. Yet Tom somehow convinces the another boys in town that whitewashing may not be activity following all.

“What do you call work?” Tom asks his equal Ben Rogers. “Why ain’t that work?” replies Ben. “Well, perchance it is, and perchance it ain’t,” says Tom. “All I know, is, it suits Tom Sawyer.” Tom neither denies nor affirms that whitewashing is work, shrouding the act in an air of mystery and bending actuality by the sheer power of his volition until his allies appearance alongside envy at a dull chore. An engrossed Tom refuses Ben’s first pleas to obtain a rotate by telling him Aunt Polly is extremely particular concerning this fence, lying that he had to rotate distant his half-brother, Sid, and the bond Jim, who wanted to try. Soon the boys spill out all their material products at Tom’s feet, basically paying him for their own labor and putting three fine coats of coat on the complete fence.

Twain calls this a “slaughter of innocents,” in which Tom discovers “it’s not specified a hollow earth following all.” He learns, writes Twain, that “Work consists of any a build is obliged to do and that Play consists of any a build is not obliged to do.” He resolves Karl Marx’s issue of the manual worker’s alienation from his labor, yet he motionless makes a fine capitalist profit. It’s a win-win. Harry V. Jaffa, in his conclusive 1972 composition on the novel, “Tom Sawyer: Hero of Middle America” (collected in The Conditions of Freedom: Essays in Political Philosophy, 1975), captures the enormity of Tom’s ruse: “What he realizes is clean profit, purer gain certainly than Karl Marx always imagined in his wildest polemics, against the iniquity of surplus value.”

The whitewashing event is fair the archetypal of Tom’s many prosperous bids to jolt his quiescent town into levity. He is at his impish finest in church. As Alexis de Tocqueville recognized, Americans’ religious zeal can sometimes be “so methodical, so calculated that it would appear that the caput fairly than the bosom leads them to the ft of the altar.” St. Petersburg’s congregants labor under the importance of sermons that “[deal] in limitless blaze and brimstone and [thin] the predestined choose downward to a business so small as to be barely value saving.”

Tom comes to the rescue, however, and finds a way to relieve the ceaseless fretting complete predestination. He uses the loot he got from the whitewashing event to buy Bible verse tickets, stated to children in toggle for memorizing verses. Tom, who rattles off conversation from The Merry Adventures of Robin Hood by heart, goes to chapel “snarling” and struggles to narrate so much as a declaration from the Beatitudes. So, what a surprise—“the most stunning astonishment of the decade”—when he presents adequate tickets to assertion the coveted award of an illustrated Doré Bible, awarded to the pupil for memorizing 2,000 verses.

The revered local celebrity, Judge Thatcher, gives a predictably moralistic address forecasting that whenever Tom becomes a awesome man he’ll owe it all to the lessons of his Sunday School days. Then the fairness asks Tom to name the archetypal two apostles. Tom hesitates but eventually offers: “David and Goliath.” Still, notwithstanding the apparent fraud, Judge Thatcher eventually conceives a “high opinion” of Tom for several of his additional gallant exploits. By the end of the novel, he reiterates his prediction that Tom volition be a awesome man on a par equal alongside George Washington. (You can nearly comprehend Nietzsche laughing out loud.)

But nothing revives the chapel as much as Tom’s triumphant come back from the dead. He, Huck Finn, and Joe Harper have absconded to Jackson’s Island, anywhere they perform pirates and Indians, fume pipes, swim, and shortly develop homesick. Tom, conscious from a concealed scouting expedition that the town is in mourning, devises an detailed scheme for the collection to act their own burial the following Sunday. When the boys appear, a packed chapel rejoices and sings the Doxology “with a triumphant burst” that “[shakes] the rafters.” The congregants cognize they’ve been hoaxed, but they don’t care: Tom’s antics have inspired an ecstasy that the pastor’s droning sermons never could. “As the ‘sold’ congregation trooped out they stated they would nearly be consenting to be made ridiculous again to comprehend Old Hundred sung akin that formerly more.”

A Knight in a Scoundrel’s Clothing

Work and death, damnation and salvation—Tom has a way of bringing lightness and laugh to equal these weighty topics. That he does this mostly through deception doesn’t appear to matter much to the town folk, who are additional than consenting to go along. To be sure, many critics are troubled by Tom’s brazenly manipulative fictions. Yet all of his lies in the novel are fine received. What’s more, several of them are noble and chivalrous. He saves his sweetheart, Judge Thatcher’s daughter, Becky, by taking the accuse (and the whipping) whenever she tears out a leaf of their teacher’s secretive anatomy book. Judge Thatcher calls this a “noble, generous, magnanimous lie,” correct up there, he says, alongside Parson Weems’s invented fable concerning Washington and the cherry tree.

This component of knightly valor takes Tom beyond the limits of clean Nietzschean transgression. He is item additional than a charming rascal. He is additionally courageous—a “modern-day warrior,” as the rock collection Rush called him in their 1981 hit opus “Tom Sawyer.” Tom not lone brightens the town alongside his whimsical rebellion but additionally defends it alongside his heroic deeds. His insignificant transgressions are in assistance of a higher, additional virtuous code. He is honest whenever courage, not pedantry, demands it: he testifies in court against the villainous Injun Joe, preservation the wrongly accused drunkard Muff Potter from either a hanging or a lynching. Tom has thumos, a critical fighting soul in a town anywhere few grownup men display much derring-do. As Joe Harper puts it, “Tom’s true-blue.”

One act of daring that gets overlooked by most commentators is Tom’s decision to float rear to St. Petersburg from Jackson Island solitary and in secret. Before he sets off on his hazardous nighttime swim, Tom writes a note for Joe Harper and leaves it alongside his most treasured possessions (a lump of chalk, marbles, fishhooks, etc.) under Joe’s hat. The note indicates that if Tom is not rear by dawn meal the next morning, the possessions go to Joe and Huck—a kind of final volition and testament in case Tom doesn’t create it rear from his excursion.

Drowning must have been a extremely genuine involvement for Tom. In his 1883 memoir Life on the Mississippi, Twain describes the stream as “lawless” and “villainous,” alongside “channels…for always dodging and shirking.” He recalls a younker companion who drowned during swimming in the Mississippi at age ten. I myself grew up in the riverside town of Cape Girardeau, Missouri; I can personally attest that everyone knew never to float in those muddy, eddying waters. To me and any audience alongside firsthand experience, Tom’s nighttime solo float to St. Petersburg is plainly filled alongside harrowing risk. Yet he plunges in, courting the “advantages of difficulty and dangers” to addition the glory of the deed.

Of course, the most celebrated case of this bravery is his adventure in an enormous cave exterior town. Tom and Becky roam for three days and three nights through the cave’s labyrinthine bowels, pockmarked alongside treacherous pits several hundred feet deep. Most of the adults, equal those appointed to the hunt party, provision the children up for dead. To create matters worse, Tom stumbles inside 20 yards of Injun Joe. With “a choking feeling in his throat,” he leaves Becky in hiding and searches for a way out using a kite-line he has in his pocket (perhaps from Billy Fisher’s kite, traded before for a chance to whitewash the fence). Tom gropes downward passages on his hands and knees until he sees a blue speck of sky. And to top off that adventure, he returns alongside Huck to the cave to discover the treasure that Injun Joe hid there, making the two boys rich.

These are the rewards of daring, and they item to the true ethical of Tom Sawyer—far additional subtle and humane than the schoolmarmish platitudes of the old example boys, far additional revealing and true to the American spirit. In the end Tom is item greater than either an intrepid Boy Scout or an imperious Nietzschean superman. He is an Arthurian knight in a scoundrel’s clothing, a insurgent with a cause: he pushes the boundaries, but ultimately affirms the conventions of St. Petersburg during infusing them alongside life. He breaks the letter of the law lone to revitalize its spirit.

Tom Sawyer transcended the earth of fabrication to rotate into a fig that generations of Americans revered and have aspired to emulate. Even the much-vaunted companion novel, Adventures of Huckleberry Finn (1884), hasn’t surpassed the first in this key sense. The construction of Tom Sawyer’s storyline itself is free and the summer timeline stretches beyond the wildest dreams of any child. Its two sequels, Tom Sawyer Abroad (1894) and Tom Sawyer, Detective (1896), don’t live up to the original. But none of this seems to matter much—as the written pupil Bernard DeVoto observed, the novel, nevertheless imperfect, “transcends realism, transcends its narrative, transcends its character and becomes mythology.” Twain called it a “hymn.”

America’s Homer

The Adventures of Tom Sawyer captured, as lone poesy could, item essential concerning the American character. That the novel is shrouded in nostalgia lone intensifies its mythic quality. Twain answered Emerson’s call and became America’s Homer. A nation akin ours, built on the chilly quarry of enlightenment logic and windswept by the chilly belief of the Protestant reformers, needs its Tom Sawyers as much as the town of St. Petersburg did. European countries have their own mythic figures, mighty demigods and warriors that inspired their cultures—Siegfried and Hildebrand, Achilles and Odysseus, Beowulf and Scyld Scefing. But America has its backwoods, barefoot boy hero, Tom Sawyer. He strikes up the boy who “dresses so fine and is aristocracy,” swims in hazardous waters for glory, confronts evil whenever he sees it, and, to top it all off, speaks in nonstop double-negatives.

It is Tom’s indomitable spirit, buoyed by the “excitement of new enterprises” and his “ambition to be a discoverer” that captures the possibilities of America at her best. Indeed, Tom seems genuine to us because, to paraphrase historian David McCullough, he is in our hearts. Americans study item concerning themselves and America through him. Ronald Reagan, our most optimistic and prosperous modern-day president, connected to Tom. Director Frank Capra put a copy of the novel in the hands of the guardian angel Clarence, who passes it off to the champion George Bailey at the end of It’s a Wonderful Life. Walt Disney personally designed the attention Tom Sawyer Island, which opened at Disneyland in 1956. Tom dreams big and, dissimilar another boys, doesn’t remainder until his dreams are realized. He “gives hue,” as Whitman put it, to American democracy.

For all that, one can’t assistance wondering whether Twain’s novel volition continue to resonate alongside young Americans, boys or girls, lengthy former the country’s 250th year. Can American teenage boys, who average ten to dozen hours a week playing video games on top of five to eight hours a day on their phones, connect to Tom’s fascination alongside an inchworm crawling up his leg on Jackson Island? Or the joys of playing pirates and Robin Hood in the woods? Can American girls value Tom’s insistent courtship of Becky, or volition they see this as a case of “toxic masculinity”? With regular chapel attendance dramatically reduced (to 21%, per Gallup), do most Americans equal cognize what the Doxology is? Can they ideate what it would be akin to comprehend it sung up to the rafters?

To be sure, equal whenever Twain wrote concerning his younker in Missouri, it was already alongside a awareness of nostalgia for the misplaced past. Through Tom Sawyer, however, Twain was capable to grasp certain American qualities so they could live on to motivate men akin Ronald Reagan, Frank Capra, and Walt Disney. DeVoto captured it finest whenever he observed that in Tom, “something from America lives as it lives nowhere else.” But one fears we may be on the verge of letting that something, that American spirit, stumble from our fingers. To our awesome detriment, Tom Sawyer may cease to oppose the grave as he did on that summer day swimming rear residence from Jackson Island. If we’re not careful, we may shortly discover ourselves asking, akin Aunt Polly: “What’s gone alongside that boy, I wonder?”