Back to Rundown
Rundown

Cosmic Rundown: GnuPG RCE, Lean Proofs, Inkling 2 Mini

Cosmic AI's avatar

Cosmic AI

November 21, 2026

This article is part of our ongoing series exploring the latest developments in technology, designed to educate and inform developers, content teams, and technical leaders about trends shaping our industry.

Today's list includes two remote code execution bugs in tools that process untrusted files. It also covers a formal proof effort that is worth understanding even if you never touch Lean, and a new small model that fits in a few gigabytes of memory. After that come reads on how AI is changing engineering roles, a table of builder tools, and quick hits.

When Input Becomes a Command

Three items share one root cause. Data that a program was supposed to read ended up being treated as instructions.

A short checklist for today:

  1. Find every place GnuPG and Ghostscript run, including container base images and build runners, and update them.
  2. List every feature that processes files uploaded by users. Where you can, run conversions in a sandbox with no network access.
  3. Treat log fields, headers, and filenames as untrusted input everywhere they flow. That includes search and analytics systems.

Proofs You Can Check

The math story from the past day has moved from claims to checking.

Not everyone is convinced. A paper on PhilArchive argues for the invalidity of the Alpoge proposed proof (discussion). For broader reactions, see Scott Aaronson's The stochastic parrots have apparently proved the Riemann Hypothesis (discussion) and The Economist's AI is swallowing maths. Is economics next? (discussion).

For software teams, the lesson is about checking, not number theory. A proof assistant moves trust from the author to the checker. It also leaves one question that people still have to answer: does the formal statement actually say what the headline claims? That is a review problem, and humans still own it.

The same idea applies to ordinary code. Deterministic Simulation Testing Is for Everyone (discussion) argues that ordinary teams can now replay a system under controlled time, network, and randomness. It is no longer a technique reserved for database companies.

Small Models and Sharp Benchmarks

Where Your Prompts Go

Two reports in the newest queue matter if you send customer data to model APIs.

Signal's post on restricting AI agents in mobile operating systems from capturing data (discussion) looks at the same problem from the device side.

Three practical steps follow from these reports:

  1. Keep a list of which providers receive which data.
  2. Plant canary strings in test traffic so you can tell if prompts are retained.
  3. Strip secrets before a prompt leaves your network.

The Job Is Changing

Builder Reads

ReadGood for
PostgreSQL Extensions in Go (discussion)Teams that want Postgres extensions without writing C
Zero C#: Power of C# without any GC (discussion).NET developers chasing predictable latency
Probabilistic data structures in Go, part 2 (discussion)Counting and deduplicating at scale
The tech architecture of an art website (discussion)Small site owners comparing stacks
Brazil's tax authority open-sources its tax calculator under MIT (discussion)Public sector and fintech developers
Slopstrap: make your site look hastily vibecoded (discussion)Anyone who has noticed that AI-built sites look alike
DreamCoder (discussion)Emacs users evaluating coding harnesses
Winedroid WASM demo (discussion)Running Android apps in the browser

Quick Hits

What This Means for Content Teams

Keep file processing off your own servers. The GnuPG and Ghostscript bugs live in the pipelines that convert uploads. With a headless CMS, uploads go through a managed media API and are served from an image CDN. Content reaches your front end as data through the REST API, so your team has fewer conversion tools to patch when the next RCE lands.

Check before you publish. The Lean story shows that a checker earns trust only when someone confirms it checked the right statement. Content works the same way. Cosmic AI Agents work inside your content model and keep activity logs. Cosmic Workflows add approval gates, so an editor reviews AI-assisted drafts before they go live.

Know where your content and keys go. The prompt logging reports are a reminder to limit what leaves your system. Each Cosmic Bucket has separate read and write keys, and the authentication docs explain why the write key should never ship in a browser bundle. For coding assistants, the hosted MCP Server exposes a fixed set of content tools rather than open access.

Design the interface first. If developers are becoming architects, the content model becomes one of the interfaces they own. A clear model lets people, agents, and visiting AI tools all read the same structured content, and a front door for AI agents answers from what you have published.

To get started, read the documentation or create a free account.