RepoJournal
AI Red Teaming AI Red Teaming
16 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-10-14
stories 60

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

PyRIT marks unscored objectives UNDETERMINED, and a breaking dataset-controls change lands

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

PyRIT's biggest operational changes land on the scoring and replay paths: an objective scorer that returns no score no longer reads as an attack failure, and scenario dataset controls arrive across CLI, REST and GUI as a breaking change.

[BREAKING] FEAT: Add scenario dataset controls to CLI, REST, and GUI (#3143) microsoft/PyRIT

by Richard Lundeen

Scenario dataset controls are now exposed across the CLI, REST API and GUI, and the change is flagged breaking. If your pipelines spend datasets or select seeds programmatically, check the new interface against your existing calls before you upgrade.

FIX: record UNDETERMINED when the objective scorer returns no score microsoft/PyRIT

by u7k4rs6

When an objective scorer is set, a response comes back, and the scorer returns no score, the attack result is now UNDETERMINED with "Objective scorer returned no score" instead of FAILURE, affecting PromptSendingAttack, MultiPromptSendingAttack, RedTeamingAttack and ChunkedRequestAttack. Real false scores, blocked responses scored false by the scorer, and missing responses still read as FAILURE...

FIX: keep Responses web search calls replayable and behind the answer microsoft/PyRIT

by u7k4rs6

Responses web search calls now store the whole web_search_call item (id, status, action) and replay exactly the fields the input item accepts, with tool records ordered after the text so get_value() returns the answer again. Older stored rows carrying only type and id are skipped with a warning rather than failing the whole request, so pre-existing logs replay partially.

FEAT: Add dataset example table and seed detail view microsoft/PyRIT

by juliosuas

The /datasets/detail?selection_key= selection page gains a read-only paginated table of logical examples with an expandable detail view, backed by typed datasetsApi methods. Pages load one at a time and members fetch only on expansion via GET /api/datasets/seeds/{example_id}?selection_key=, so the catalog never prefetches seed pages.

MAINT: P311-16 remove Python 3.10 trailing-Z workaround in _parse_datetime (#3176) microsoft/PyRIT

by Kushal Talati

PyRIT dropped the Python 3.10 trailing-Z workaround in _parse_datetime, a small cleanup that only matters if you still run the library on 3.10. promptfoo's day was maintenance only: unused view and telemetry hook exports removed, eval import normalization reused, and assertion fixtures consolidated, with no dependency changes.

Quick answers

What shipped in AI Red Teaming on October 14, 2026?
PyRIT's biggest operational changes land on the scoring and replay paths: an objective scorer that returns no score no longer reads as an attack failure, and scenario dataset controls arrive across CLI, REST and GUI as a breaking change. In total, 29 commits and 31 pull requests landed.
Who contributed to AI Red Teaming on October 14, 2026?
5 developers shipped this update, including Michael D'Angelo, u7k4rs6, juliosuas, Kushal Talati, and Richard Lundeen.
What were the notable AI Red Teaming updates?
[BREAKING] FEAT: Add scenario dataset controls to CLI, REST, and GUI (#3143), FIX: record UNDETERMINED when the objective scorer returns no score, and FIX: keep Responses web search calls replayable and behind the answer.