Microsoft Exchange Server 2016 and 2019 enter their 'permanently vulnerable' era
Comments on “Microsoft Exchange Server 2016 and 2019 enter their 'permanently vulnerable' era”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
Microsoft has told customers still running Exchange Server 2016 and 2019 to treat those versions as "permanently vulnerable," since they no longer receive security testing or patches after the final extended updates in October 2025.
Why it ranked
No. 109 of 137 with a score of 0.58. The panel rated it highest on new information (0.87) and reader interest (0.68), lowest on technical depth (0.32). Placed No. 109, No. 105 by score alone: the 34th 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
- Timely security and enterprise IT news on end of Exchange 2016/2019 patching; relevant to IT and security builders, with a sourced quote from Microsoft but little technical depth.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported security and enterprise IT warning: unsupported Exchange versions will no longer receive vulnerability testing or patches, including amid critical flaws. It is practically important for affected administrators but narrowly scoped and technically shallow.
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.58total under rubric v2.3
- Significance0.58
- Reader interest0.68
- Audience breadth0.44
- Practical relevance0.67
- Substantiated0.62
- Technical depth0.32
- New information0.87
- Counts against: Promotional0.05
- Counts against: Overclaim0.22
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.63 | 0.40 | 0.72 | 0.58 | 0.32 | +0.24 | +0.140 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.61 | 0.60 | 0.82 | 0.68 | 0.22 | +0.26 | +0.176 |
| Audience breadthHow many people who build technology does it concern? | 0.33 | 0.50 | 0.48 | 0.44 | 0.17 | +0.13 | +0.057 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.53 | 0.70 | 0.78 | 0.67 | 0.25 | +0.22 | +0.147 |
| 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.53 | 0.50 | 0.84 | 0.62 | 0.34 | +0.05 | +0.031 |
| Technical depthHow technically substantive is it? | 0.49 | 0.20 | 0.28 | 0.32 | 0.29 | +0.05 | +0.016 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.80 | 0.93 | 0.87 | 0.13 | +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.10 | 0.05 | 0.01 | 0.05 | 0.09 | −0.19 | −0.010 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.37 | 0.20 | 0.08 | 0.22 | 0.29 | −0.11 | −0.024 |
| Sum of contributions | +0.577 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.577 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-11-13/109/"><img src="https://rubric.hrih.si/badge/2026-11-13/109.svg" alt="Ranked #109 on Rubric, 13 Nov 2026" width="252" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 15 Nov 2026, 20:42 UTC. It played no part in the ranking.