Edition of Friday 13 November 2026

From Rent to Root: Introducing NvRoot (CVE-2026-47591)

Comments on “From Rent to Root: Introducing NvRoot (CVE-2026-47591)”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Stealthium disclosed NvRoot (CVE-2026-47591), an NVIDIA driver flaw where a pin request marked CPU read-only but GPU writable gives the GPU write access to a read-only file's cache. The researchers say an unprivileged user can overwrite a setuid binary like /usr/bin/su in memory and gain root, including from a container on a shared host. They trace it to release 515.43.04 (2022); fixes are in 610.57.04, 595.91.07 and 580.178.04. NVIDIA's 7.8 High rating differs from Stealthium's 9.3 Critical. Nearly all claims are Stealthium's alone, unverified.

Read the original at stealthium.io. 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. 13 of 137 with a score of 0.71. The panel rated it highest on new information (0.93) and reader interest (0.89), lowest on audience breadth (0.65). The judges disagreed most on promotional (spread 0.50), so the story is marked contested. Placed No. 13, No. 11 by score alone: the sixth Security story of the day (−0.060). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Significant GPU driver local privilege escalation with patch details and detection guidance; strong practical relevance for GPU tenancy. Exploit details withheld and some claims (CVSS reframing, scope) rely on the vendor's own assessment, so substantiation is moderate and some overclaim is possible.
AI judgeJudge 3gpt-5.6-luna
A technically detailed, reproducible vulnerability disclosure with major implications for shared GPU infrastructure and container isolation. Strong evidence and mitigations are provided, though customer-focused detection marketing and severity framing temper the scores.

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.71total under rubric v2.3Contestedjudges differ by 0.50 on promotional

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.78
  • Reader interest0.89
  • Audience breadth0.65
  • Practical relevance0.87
  • Substantiated0.72
  • Technical depth0.77
  • New information0.93
  • Counts against: Promotional0.33
  • Counts against: Overclaim0.43

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.730.720.880.780.16+0.24+0.187
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.830.900.930.890.10+0.26+0.231
Audience breadthHow many people who build technology does it concern?0.590.670.700.650.11+0.13+0.085
Practical relevanceHow useful is it to someone who builds software or tech products?0.870.850.900.870.05+0.22+0.192
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.650.700.820.720.17+0.05+0.036
Technical depthHow technically substantive is it?0.860.600.850.770.26+0.05+0.038
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.880.930.980.930.10+0.05+0.047
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.120.250.620.330.50 , above the contested threshold−0.19−0.063
OverclaimDo the headline or conclusions claim more than the body supports?0.390.450.450.430.06−0.11−0.047
Sum of contributions+0.705
Claim-check penalty0.000
Total, as published0.705

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

Claim check

Claim check: 5 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkNumber

    NVIDIA scores CVE-2026-47591 as CVSS 7.8 High.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “NVIDIA has this vulnerability scored as CVSS 7.8 High”

    The source says

    No passage could be compared.

    Source cited by the article: nvidia.custhelp.com/app/answers/detail/a_id/5861

  2. No source givenDate

    The NvRoot flaw is present in the first public open GPU kernel module release, 515.43.04 from May 2022, and remained in every build before the August patch.

    The article gives no link or citation for it.

    The article says

    “It’s present in the very first public release, 515.43.04 from May 2022, and has remained through every build before the patch fix shipped in August”

    The source says

    No source to compare with.

  3. Couldn’t checkDate

    NVIDIA shipped the fix on August 3, 2026 in driver versions 610.57.04, 595.91.07, and 580.178.04.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “August 3, 2026: NVIDIA ships the fix in driver versions 610.57.04, 595.91.07, and 580.178.04”

    The source says

    No passage could be compared.

    Source cited by the article: nvidia.custhelp.com/app/answers/detail/a_id/5861

  4. Couldn’t checkDate

    NVIDIA published its security bulletin and assigned CVE-2026-47591 on September 30, 2026.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “September 30, 2026: NVIDIA publishes its security bulletin, assigns CVE-2026-47591, and notifies of covered branches of versions”

    The source says

    No passage could be compared.

    Source cited by the article: nvidia.custhelp.com/app/answers/detail/a_id/5861

  5. No source givenVersion

    The exploit was confirmed to give root on driver 610.43.02 and confirmed fixed on 610.57.04, where the write is rejected at pin time.

    The article gives no link or citation for it.

    The article says

    “Confirmed to root on driver 610.43.02, and confirmed fixed on 610.57.04, where the write is rejected at pin time”

    The source says

    No source to compare with.

  6. No source givenGeneralization

    The bug is deterministic, kernel-version independent, and works the same from an unprivileged container as on a bare host.

    The article gives no link or citation for it.

    The article says

    “The bug is deterministic, kernel-version independent, and works the same from inside an unprivileged container as it does on a bare host”

    The source says

    No source to compare with.

  7. No source givenNumber

    Stealthium assesses the vulnerability as 9.3 Critical under CVSS 4.0 (8.8 under 3.1 with scope change).

    The article gives no link or citation for it.

    The article says

    “Our assessment, which accounts for impact beyond the vulnerable component, is 9.3 Critical under CVSS 4.0 (8.8 under 3.1 with scope change”

    The source says

    No source to compare with.

  8. No source givenCausal conclusion

    There is no practical workaround short of updating, since the defect is in the driver's permission-derivation logic and any process that can open /dev/nvidiactl reaches the vulnerable path.

    The article gives no link or citation for it.

    The article says

    “there’s no practical workaround short of updating: the defect is in the driver's own permission-derivation logic, not something a sysctl, seccomp profile, or cgroup can close off”

    The source says

    No source to compare with.

Also covered by

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:42 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 “From Rent to Root: Introducing NvRoot (CVE-2026-47591)”

More on Rubric

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