Edition of Thursday 19 November 2026

Java4Shell, NGINX2Shell and more: Why we are not at "Yellow", (Wed, Nov 18th)

Comments on “Java4Shell, NGINX2Shell and more: Why we are not at "Yellow", (Wed, Nov 18th)”

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

SANS Internet Storm Center's Johannes Ullrich explains why the organization is keeping its InfoCon threat level at Green despite a run of recent vulnerabilities, including php2shell, a critical Java flaw dubbed Java4Shell, and a disclosed NGINX issue.

Read the original at isc.sans.edu. 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. 138 of 144 with a score of 0.55. The panel rated it highest on audience breadth (0.73) and new information (0.69), lowest on substantiated (0.36). The judges disagreed most on new information (spread 0.58), so the story is marked contested. Placed No. 138, No. 140 by score alone: the 42nd 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
Opinion piece on security alert levels and vulnerability response practices; on-topic for builders and security teams, mostly opinion with little technical depth or novel verifiable data.
AI judgeJudge 3gpt-5.6-luna
A timely security analysis with actionable guidance on patching, exposure reduction, blast-radius control, and sustainable incident response. It is broadly useful but offers limited technical evidence, reproducible detail, or concrete analysis of the named vulnerabilities.

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.55total under rubric v2.3Contestedjudges differ by 0.58 on new information

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.50
  • Reader interest0.60
  • Audience breadth0.73
  • Practical relevance0.68
  • Substantiated0.36
  • Technical depth0.38
  • New information0.69
  • Counts against: Promotional0.06
  • Counts against: Overclaim0.23

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.530.350.610.500.26+0.24+0.119
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.510.500.780.600.28+0.26+0.155
Audience breadthHow many people who build technology does it concern?0.880.600.700.730.28+0.13+0.094
Practical relevanceHow useful is it to someone who builds software or tech products?0.630.600.800.680.20+0.22+0.149
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.200.350.540.360.34+0.05+0.018
Technical depthHow technically substantive is it?0.470.250.430.380.22+0.05+0.019
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.880.300.880.690.58 , above the contested threshold+0.05+0.034
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.090.050.030.060.06−0.19−0.011
OverclaimDo the headline or conclusions claim more than the body supports?0.280.200.200.230.08−0.11−0.025
Sum of contributions+0.553
Claim-check penalty0.000
Total, as published0.553

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 #138 on Rubric, 19 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-19/138/"><img src="https://rubric.hrih.si/badge/2026-11-19/138.svg" alt="Ranked #138 on Rubric, 19 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 19 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 “Java4Shell, NGINX2Shell and more: Why we are not at "Yellow", (Wed, Nov 18th)”

More on Rubric

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

  1. Score 0.78

    NoisyTCP