EVIDENCE. REPAIR. PROTECTION.

Program BustersLook closely. Make software safer.

Apps, files, accounts and the code between them.

We examine our own applications and report what the evidence supports. Confirmed defects, open limitations and vendor disclosures each get a clear status. Browser Busters continues as the browser-testing part of this work.

Read the findings
A hand checks glass panels in a precision bench frame; original concept art.
THE INSPECTION BENCHConcept artwork. Test evidence is separate.

PB-CARTRIDGE-001 / PRIVACY-RELATED WORKFLOW DEFECT

A failed new lock left the old file ready to share.

Fixed before first public release · Office Suite 1032 Release 50

In a development candidate, we locked fictional file A, selected file B, then entered mismatching passphrases. B was not encrypted, but A’s previous output still appeared under a generic filename. Downloading and decrypting that output confirmed that it contained A. That created a wrong-file handoff risk.

Reproduced

Edge and Windows Playwright WebKit each retained the old output after the failed new attempt. No real files, recipients or external messages were involved.

Repaired

Changing an input clears the old output and cancels an unfinished operation. The output names its original file locally. A late response cannot replace a newer operation’s state.

Repair checks require the old download to disappear, a failed attempt to leave no output, and a successful replacement to contain B. Wrong-password, wrong-recipient, altered-file and decompression-limit checks also cover the cartridge implementation. This is a pre-release application defect; no remote exploit or affected production user was established.

Inspect the bounded evidence summary · Try Office Suite 1032

PB-INBOX-001 / SEND-CANCELLATION DEFECT

“Not found” did not mean “stopped.”

Fixed before the private inbox’s first public release · November 15, 2026

A send can still be travelling when its sender checks for a receipt. In an unpublished inbox candidate, an operation that had not reached storage could not be cancelled: the server returned 404. Returning to a draft at that point did not stop the delayed original request. That created a risk of delivery after the sender had changed their mind.

Reproduced with fictional accounts

The original regression captured the missing-operation cancellation failure. An isolated ordered replay restored that pre-fix branch: the initial check said “not found,” cancellation returned 404, and the delayed original was then delivered. No live users or outside recipients were involved.

Repaired at the server

Cancellation now leaves a durable record even before a message exists. Both acceptance and final delivery check it. In the matching repaired replay, cancellation succeeded, the late original was refused with 409, and the recipient had zero new messages.

Practical recommendation: an interrupted send is uncertain until its server receipt or cancellation is confirmed. Reuse the same send identifier when retrying; do not silently create a fresh send. Delivered, opened and downloaded are separate events, not proof that a person read the content.

This is a bounded pre-release application finding. The replay uses two synthetic identities and an isolated SQLite adapter; it does not reproduce a network exploit or independently certify the hosting platform. Inspect the before/after observations.

PB-INBOX-002 / PRIVACY UPGRADE

Message text locks before it leaves your device.

End-to-end encryption for new messages · Suite inbox version 2

The original inbox stored message text privately on the server. New messages encrypt on the sender’s device for both participants and carry a sender signature. The server stores ciphertext. Reading and signature checks happen on the user’s device, including in Sent.

What the checks establish

Synthetic accounts exchanged signed messages and files. Both participants could decrypt the message; an unrelated key could not. Wrong keys, altered text, substituted delivery details, extra recipients and invalid signatures were rejected. A unique test message did not appear in request bodies, database rows, API lists, exports or receipts.

What stays visible

The service still sees identities, correspondents, timestamps, encrypted sizes, public keys and receipts. Version 2 retained earlier server-readable messages. Version 3 now protects that history once both keys exist; missing or invalid keys stay visibly pending, as detailed below. Encryption does not undo prior access or protect a compromised device while a message is open.

Practical recommendation: save your recovery key and passphrase, compare changed fingerprints with your contact, and lock the inbox when you step away. Replacing a key does not unlock older messages. This static-key system does not provide forward secrecy.

These are bounded application checks with synthetic identities, including Edge and Windows Playwright WebKit. They are not an independent security certification or two real provider-account sign-ins. Read the evidence summary · Open the private inbox.

PB-INBOX-003 / EARLIER-MESSAGE PRIVACY

Close the gap behind the new lock.

Active-row protection implemented · Honest history labels

Encrypting new messages left an earlier-storage gap. An unchanged legacy receipt hash could also keep a guess-checking value for short text after encryption. The upgrade now encrypts the exact earlier record for both participants and replaces its readable body and old hash together.

Preserve the work

Both people opened the same protected text in synthetic tests. Original delivery, opening and download receipts stayed intact. A rotated message key did not replace the original locked-file key. Interrupted writes, simultaneous upgrades and deletion races preserved or reconciled the record.

Keep the claims precise

Earlier archives were encrypted after delivery; they do not acquire an original sender signature. Missing keys remain pending. Invalid keys pause only their affected messages, allowing other history to proceed. Prior access, downloaded copies and provider-retained historical backups cannot be undone.

Recommendation: save your recovery key, keep older keys for older files, and check any pending protection notice. Readable earlier text is withheld from app reads and exports while protection waits for both keys. Cloudflare’s historical-backup documentation.

PB-CI-001 / HUMAN CONFIGURATION CHOICES

Fewer credentials before a merge.

Workflow hardening tested · Trusted-writer limit remains

Our Azure workflow referenced its deployment credential in pull-request preview uploads and cleanup jobs. Eight inert event fixtures reproduced those paths without resolving or transmitting a real secret. This establishes configuration reachability, not a credential leak or an unauthorized production deployment.

The repair

Pull requests now run validation without a deployment-secret reference. Publishing runs on a separate hosted runner only for the exact checked main-branch push. A fresh checkout and upload scan precede the upload. Automatic PR deployments and their cleanup job were removed.

The boundary that remains

Repository writers remain trusted: they can alter workflows and access repository-scoped secrets. Editable event checks cannot enforce a provider-level boundary against those writers. No environment protections, billing changes, credential rotation or remote-preview removal are claimed.

Recommendation: where the repository plan supports it, scope deployment secrets to an environment with an explicitly selected main branch and remove broader copies after verification. Stronger writer isolation needs a separately controlled publishing system. Normal fork PRs do not receive repository secrets by default, and Azure PR uploads normally create previews. GitHub’s secret-access model · Azure preview behavior · Read the actual before/after fixtures.

PB-OPS-001 / VERIFY TEMPORARY ACCESS RETIREMENT

Check that the door really closed.

Retired in code · Former credential rejected in production

A temporary, credential-protected operator route checked whether earlier messages needed encryption. Production reported zero legacy records. Removing its runtime settings and republishing the same saved version reported success, but our direct check still accepted the former credential. Trusting only the control-panel result would have left the capability available until its expiry.

Observed and repaired

We removed the route from the application and published new source. A fresh browser check using the former credential returned 404. Anonymous GET and POST checks also returned 404 in Edge and Windows Playwright WebKit. The regular inbox sign-in page remained available.

Keep the finding bounded

This is an owned deployment observation and a verification lesson. The provider-level cause is unresolved; no credential leak, unauthorized visitor or wider platform vulnerability was established. No customer content was published.

Recommendation: give temporary access an expiry, remove the capability when its job ends, and test the former credential against the deployed application. A successful settings update alone does not prove access stopped.

PB-DEP-001 / AFFECTED DEPENDENCY BYTES

Check the code that actually ships.

Patched runtime published · Application exploitation not established

Our inbox build included React Server Components 19.2.6, both as a direct package and inside its bundler plugin. We matched the installed serializers to the official package and found the earlier serializer in the built Worker. The vendor lists that version as affected by GHSA-xqc2-xf4c-x3h3. This establishes affected component presence, not a successful attack against the inbox.

What we changed

The repair updates React and both serializers to 19.3.1, Vinext to 1.3.1 and its RSC plugin to 0.5.38 together. The release gate checks the complete reviewed lockfile and selected installed runtime, resolver and parser bytes. A patched version label cannot conceal an old bundled copy.

What we did not establish

The RSC advisory requires a rare response containing multiple typed arrays and an attacker-controlled value. This review did not establish that path in the inbox, exploitation or a data leak. Message and cartridge APIs use JSON or file responses. The app does not implement inline server-action closures; no Vinext closure attack was reproduced.

Verified in release 5: the rebuilt inbox passed 67 automated checks and synthetic message, recovery and locked-file flows in Edge and Windows Playwright WebKit. Published private API routes reject anonymous requests and forged identity headers. This does not establish a real-user penetration test.

Follow-up verified in inbox release 7: the three remaining tooling advisory families are now patched. We migrated the Zod record API and tested narrowly scoped minimatch and esbuild overrides through their actual callers. The reviewed lockfile audit fell from 13 affected package entries to zero known entries. The earlier count included propagated dependants, not 13 demonstrated inbox vulnerabilities; zero known audit entries is not a security certification.

The release passed 95 automated checks and 37 synthetic privacy and People checks in each of Edge and Windows Playwright WebKit. The expanded release gate checks 14 direct pins, three transitive pins and 63 selected installed files. Seven official archives were integrity-checked and all 1,017 reviewed archive files matched the clean installation. Production checks confirmed the published assets and rejected anonymous or forged private-API requests. Consent, blocking, encryption and database source stayed unchanged.

Keep watching: the older transform helper is deprecated even with its patched dependency. Replace it through a separately tested parent upgrade. The Zod repair rejects oversized bounded collections before element parsing; it does not make every unbounded input safe. No matching hosted exploit or compromise was established. minimatch advisory · esbuild advisory · Zod bounded-collection fix.

Recommendation for developers: update affected direct and bundled dependencies together, rebuild, inspect the code included in the artifact, and rerun authorization and privacy tests. For Windows development, update Vite's affected launch-editor dependency too; a development-server issue is distinct from the hosted Worker.

React's advisory and fixed versions · Vinext's paired-update requirement · Windows development advisory · Read the dependency evidence and limits

PB-UX-001 / TRUTHFUL PRODUCT COPY

A privacy statement must keep up.

The editor’s source-sharing help still said Office Suite 1032 did not host an inbox after the separate inbox launched. That contradicted the product and could confuse the destination of shared material. The corrected copy identifies the external-app handoff and the separate encrypted Suite inbox. This is a communication defect; no unintended transfer was established.

ATTRIBUTED VENDOR DISCLOSURES

Known flaws. Useful next steps.

These are selected publicly disclosed issues located during this review, not discoveries by Ten Thirty Two. The complete vendor lists are linked. Fix versions below describe those advisories; use the current supported update offered for your product and release channel.

CHROME DESKTOP / VENDOR RATED CRITICAL / FIX AVAILABLE

Memory-lifetime defects in service workers and layout

CVE-2026-126885 and CVE-2026-126879 are listed in Google’s November 11, 2026 security release. Google identifies released memory being reused in the affected components. The cited stable update is 157.0.8103.78/.79 on Windows and Mac, and 157.0.8103.78 on Linux. These version numbers do not establish another Chromium browser’s patch status. [1] Google’s full advisory

Action: check Chrome’s update screen and complete the relaunch, or follow your Linux package manager or organization’s update process. [2] Official update instructions

FIREFOX / VENDOR RATED HIGH / FIX AVAILABLE

Sandbox and navigation privilege boundaries

Mozilla’s November 10, 2026 advisory lists CVE-2026-124853, a sandbox escape in text rendering, and CVE-2026-124854, a navigation-related privilege escalation. Both are included in Firefox 160’s fixes. The advisory offers limited public detail; we have not reproduced these flaws or inferred an exploit chain. ESR and mobile products require their own advisories. [3] Mozilla’s full advisory

Action: install the supported update through Firefox, your app store or your distribution’s package manager, then restart as instructed. [4] Official update instructions

OPENPGP.JS / VENDOR RATED CRITICAL / FIX AVAILABLE

A false signature result can misrepresent who signed the data.

The project’s May 19, 2025 advisory, GHSA-8qff-qr5q-5pr8 / CVE-2025-47934, describes signature verification accepting modified data as signed. It lists affected ranges 5.0.1–5.11.2 and 6.0.0-alpha.0–6.1.0, with patches in 5.11.3 and 6.1.1. [5] Maintainer advisory

Action for developers: inspect the exact deployed library and upgrade an affected build. Office Suite 1032 bundles the verified 6.3.2 package; its cartridge feature makes no sender-signature verification claim. A clean version check is not a complete application audit.

A vendor’s fix notice does not prove that a particular device is updated, compromised or safe. Exploitation status was not independently established in this review. These entries are not an exhaustive inventory of all software flaws.

PB-PUBLISH-001 / PUBLICATION BOUNDARY

An unlisted address is still public.

Three person-specific assessment reports were reachable without signing in through extensionless URLs. Long filenames and search-engine exclusion did not restrict access. Publication approval was not established in this review, so we removed the reports and their two unique supporting assets from the public deployment tree while preserving the source in the private repository.

This is a publication-boundary finding, not a demonstrated authentication bypass or proof of malicious access. The affected people, report addresses and assessment details are withheld here. Removing a public file cannot recall copies already downloaded or held in someone else’s cache.

Recommendation: keep internal reports outside public build inputs. Where online access is necessary, enforce authorization on the server and test every alternate URL, including extensionless paths. Search-engine instructions and hard-to-guess names are not access controls.

OPEN / NO ISOLATION OR REVOCATION FIX CLAIMED

What still needs protection.

Browser-saved work shares an origin.

Our local check read a fictional manually saved device copy from a second page on the same origin and profile. A fresh profile did not have it. Browser projects and ordinary workspace downloads remain unencrypted. This documented boundary remains open; it is not a newly proven remote break-in.

Use now: keep sensitive work out of shared profiles, retain an independent backup, and deliberately lock a file before sending it. Encryption cannot protect plaintext while a compromised browser is handling it. Read the storage evidence and limits.

A key is not a verified person.

Cartridges assign access to a public encryption key. A display label alone cannot prove who owns it. The recipient check asks you to compare the complete fingerprint by a separate trusted channel. Source links may also grant access to anyone who holds them.

Use now: verify the fingerprint and recipient, keep private keys private, and review source permissions. The Suite inbox now binds addresses and registered keys to signed-in accounts. That verifies an account, not a person’s real-world identity. There is no private-key recovery or recall of distributed plaintext.

Scope, evidence and limits.

The review covers the owned Office Suite 1032 candidate’s file encryption workflow, source-link handling, local storage boundary and focused regression controls. The private inbox adds synthetic multi-user authorization, recipient binding, delivery receipts and cancellation checks. It also checks selected upstream advisories. Node-based cryptography checks and Edge/WebKit interface checks are complementary observations from one tester, not independent external replication.

Native desktop applications, operating-system internals, every dependency, real multi-user account authorization, browser-engine exploits, malicious extensions and physical mobile devices were not comprehensively tested. An absence of reproduced exploits does not establish an absence of vulnerabilities.

Unresolved, verified issues can be listed with their status and practical mitigation. Suspicion alone is not a confirmed finding. Private data, credentials and customer records do not belong in public reproductions.

Evidence summary · Browser-specific case archive