Edition of Thursday 12 November 2026

I found an API key leak in MLflow, and why your AI agent may have one too

Comments on “I found an API key leak in MLflow, and why your AI agent may have one too”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

A security researcher reported that MLflow's CrewAI autologging (mlflow.crewai.autolog()) recorded LLM provider API keys in agent traces, storing them in the tracking backend and any exported systems. Affected versions run from 2.19.0 to 3.16.x, and the fix shipped in 3.17.0 as CVE-2026-116691.

Read the original at github.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 87 of 106 with a score of 0.57. The panel rated it highest on new information (0.89) and practical relevance (0.80), lowest on audience breadth (0.55). The judges disagreed most on promotional (spread 0.54), so the story is marked contested. Placed No. 87, No. 82 by score alone: the 23rd Security story of the day (−0.080). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Credible disclosure of an API key leak in MLflow affecting AI agent tracing, with CVE, fix, and remediation steps. Substantively useful, but partly a promotional pitch for the author's tool and a narrow CrewAI-specific scope.
AI judgeJudge 3gpt-5.6-luna
A concrete, actionable MLflow credential-leak disclosure with remediation and reproduction context. It is highly relevant to AI infrastructure and security, but promotional tool/company content occupies a substantial portion and the broad headline slightly exceeds the evidence.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.57total under rubric v2.3Contestedjudges differ by 0.54 on promotional

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.55
  • Reader interest0.78
  • Audience breadth0.55
  • Practical relevance0.80
  • Substantiated0.75
  • Technical depth0.65
  • New information0.89
  • Counts against: Promotional0.45
  • Counts against: Overclaim0.35

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.580.450.620.550.17+0.24+0.132
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.790.720.820.780.10+0.26+0.202
Audience breadthHow many people who build technology does it concern?0.540.550.550.550.01+0.13+0.071
Practical relevanceHow useful is it to someone who builds software or tech products?0.930.700.780.800.23+0.22+0.177
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.760.720.780.750.06+0.05+0.038
Technical depthHow technically substantive is it?0.760.600.580.650.18+0.05+0.032
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.830.900.930.890.10+0.05+0.044
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.180.450.720.450.54 , above the contested threshold−0.19−0.086
OverclaimDo the headline or conclusions claim more than the body supports?0.430.250.380.350.18−0.11−0.039
Sum of contributions+0.572
Claim-check penalty0.000
Total, as published0.572

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #87 on Rubric, 12 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-12/87/"><img src="https://rubric.hrih.si/badge/2026-11-12/87.svg" alt="Ranked #87 on Rubric, 12 Nov 2026" width="245" height="28"></a>

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “I found an API key leak in MLflow, and why your AI agent may have one too”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.