RepoJournal
AI Red Teaming AI Red Teaming
52 wires and counting

$ follow AI Red Teaming

Keep up with AI Red Teaming in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-11-17
stories 35

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Concurrent live configs get isolated files, filesystem MCP pinned for a GHSA

By RepoJournal · Filed · About AI Red Teaming · Composed from the cited sources · methodology

promptfoo closed a race that let one red-team run read another's live config, pinned its filesystem MCP server to the first release patched for GHSA-p9cv-8g75-4xcg, and flagged that full-repository code scans now require Node.js 24 or later; PyRIT's breaking Pydantic fix remains the day's unanswered question for operators.

fix(code-scan): upgrade the filesystem MCP server to 2.3.0 promptfoo/promptfoo

by mldangelo-oai

The optional filesystem MCP server is pinned to 2.3.0, the first release patched for GHSA-p9cv-8g75-4xcg, and because it now declares Zod, strict pnpm and Yarn installs can drop the old package extension (Yarn Plug'n'Play still needs its ESM loader). Separately, full-repository code scans now require promptfoo to be installed and run on Node.js 24 or later; Node.js 22.22 and later keeps the CLI...

fix(redteam): isolate live config files for concurrent runs promptfoo/promptfoo

by mldangelo-oai

Two live red-team runs started in the same millisecond could write the same YAML file before generation read it, so the first run could evaluate the second run's config. Each live config now gets a UUID filename created exclusively with owner-only 0600 permissions on POSIX; cloud-loaded configs stay in the current directory so relative paths resolve, and verbose output records the generated path.

TEST: Fix flaky staged media lock and target initializer tests microsoft/PyRIT

by richlundeen

Two PyRIT tests that failed intermittently under parallel full-suite runs on Windows now pass: the staged-media cross-process lock test raced the child's rename handle, which under load produced a sharing violation (4/120 failures), and the target initializer test was fixed alongside it. Relevant to you only if you run PyRIT's suite on Windows CI.

[BREAKING] FIX: Resolve Pydantic field collisions and deprecated dependency interfaces microsoft/PyRIT

by romanlutz

Titled as breaking, this PyRIT change resolves Pydantic field collisions and deprecated dependency interfaces, which means the shapes of Pydantic-backed objects and the dependency hooks that consume them can shift under existing test harnesses. The description carries no migration detail beyond the title, so check the diff before pinning it into a scoring pipeline.

FIX: Pin historical docs themes microsoft/PyRIT

by hannahwestra25

Elsewhere: PyRIT pinned the themes on its historical docs builds, dropped a batch of test warnings, and continued the work to save API-created targets, while promptfoo updated tsdown to 0.23.7, moved OpenTelemetry to 3.1.0, and cleaned up prose across its guides, configuration, providers, and red teaming pages.

Quick answers

What shipped in AI Red Teaming on November 17, 2026?
promptfoo closed a race that let one red-team run read another's live config, pinned its filesystem MCP server to the first release patched for GHSA-p9cv-8g75-4xcg, and flagged that full-repository code scans now require Node.js 24 or later; PyRIT's breaking Pydantic fix remains the day's unanswered question for operators. In total, 15 commits and 20 pull requests landed.
Who contributed to AI Red Teaming on November 17, 2026?
7 developers shipped this update, including mldangelo-oai, ianw-oai, renovate, romanlutz, richlundeen, varunj-msft, and hannahwestra25.
What were the notable AI Red Teaming updates?
fix(code-scan): upgrade the filesystem MCP server to 2.3.0, fix(redteam): isolate live config files for concurrent runs, and TEST: Fix flaky staged media lock and target initializer tests.