CVE-2026-118383: Use-after-free vulnerability in MongoDB
Comments on “CVE-2026-118383: Use-after-free vulnerability in MongoDB”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Datadog Security Labs detailed CVE-2026-118383, a use-after-free in MongoDB replica set members (CVSS 4.0 score 9.5) that MongoDB disclosed on November 10. Standalone mongod is unaffected. In a lab on 8.0.34, two unauthenticated ping requests left stale waiters, and a later failover crashed the new primary. It depends on a lag and election the attacker cannot cause. Code execution was not demonstrated. Fixes start at 8.0.37 and equivalents; some details were not independently verified.
Why it ranked
No. 20 of 106 with a score of 0.72. The panel rated it highest on new information (0.92) and technical depth (0.89), lowest on audience breadth (0.51). Placed No. 20, No. 9 by score alone: the eighth 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
- Critical MongoDB CVE with a reproduced crash, patch versions, and detection guidance from primary testing; strong on substance and practical action, though exploitation remains a crash not code execution.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported, technically detailed vulnerability analysis with reproduction steps, affected versions, detection guidance, and patch instructions. It is highly actionable for MongoDB operators, though narrower than broad platform security news and includes modest vendor promotion.
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.72total under rubric v2.3
- Significance0.67
- Reader interest0.82
- Audience breadth0.51
- Practical relevance0.88
- Substantiated0.87
- Technical depth0.89
- New information0.92
- Counts against: Promotional0.18
- Counts against: Overclaim0.17
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.60 | 0.78 | 0.67 | 0.18 | +0.24 | +0.161 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.74 | 0.80 | 0.93 | 0.82 | 0.19 | +0.26 | +0.214 |
| Audience breadthHow many people who build technology does it concern? | 0.39 | 0.60 | 0.55 | 0.51 | 0.21 | +0.13 | +0.067 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.87 | 0.85 | 0.92 | 0.88 | 0.07 | +0.22 | +0.194 |
| 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.84 | 0.85 | 0.92 | 0.87 | 0.08 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 0.99 | 0.80 | 0.88 | 0.89 | 0.20 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.90 | 0.99 | 0.92 | 0.12 | +0.05 | +0.046 |
| 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.09 | 0.20 | 0.25 | 0.18 | 0.16 | −0.19 | −0.034 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.20 | 0.20 | 0.12 | 0.17 | 0.08 | −0.11 | −0.019 |
| Sum of contributions | +0.717 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.717 | ||||||
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-12/20/"><img src="https://rubric.hrih.si/badge/2026-11-12/20.svg" alt="Ranked #20 on Rubric, 12 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 matches source · 3 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.
Couldn’t checkNumber
CVE-2026-118383 is a critical use-after-free in MongoDB Server's primary catch-up process with a CVSS v4.0 score of 9.5.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “is a critical use-after-free in MongoDB Server's primary catch-up process, with a CVSS v4.0 score of 9.5”
The source says No passage could be compared.
Source cited by the article: github.com/advisories/GHSA-fjxh-6vgh-cx2c
Matches sourceDate
MongoDB announced a security update on November 10 and said it found the vulnerability internally and was not aware of exploitation attempts at the time.
The cited source says the same thing.
The article says “The company said it found the vulnerability internally and was not aware of exploitation attempts at the time of its announcement”
The source says “We found it internally through our proactive security program, and we are not aware of any attempts to take advantage of this vulnerability”
Source cited by the article: mongodb.com/community/forums/t/important-mongodb-security-update-available-action-required-november-10-2026/344843
Couldn’t checkQuote
The advisory says the flaw may cause the server to terminate unexpectedly or, under certain conditions, execute arbitrary code in the server process.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “the server may terminate unexpectedly or, under certain conditions, execute arbitrary code in the server process”
The source says No passage could be compared.
Source cited by the article: github.com/advisories/GHSA-fjxh-6vgh-cx2c
Couldn’t checkCausal conclusion
Standalone mongod instances are not affected because they do not perform replica set primary catch-up.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “A standalone mongod does not perform replica set primary catch-up and is not affected by this vulnerability”
The source says No passage could be compared.
Source cited by the article: github.com/advisories/GHSA-fjxh-6vgh-cx2c
No source givenVersion
The first fixed MongoDB releases are 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35 and 4.4.32 for their respective branches.
The article gives no link or citation for it.
The article says “8.0 8.0.37”
The source says No source to compare with.
No source givenNumber
Datadog reproduced a crash (segmentation fault) on MongoDB Server 8.0.34 after two unauthenticated ping requests.
The article gives no link or citation for it.
The article says “We reproduced a crash (segmentation fault) on MongoDB Server 8.0.34”
The source says No source to compare with.
No source givenBenchmark result
On patched server 8.0.37, the two unauthenticated requests were rejected immediately with Unauthorized and the target member kept running.
The article gives no link or citation for it.
The article says “Both rejected immediately with Unauthorized The target member exited catch-up once, became writable, and remained running through the observation window”
The source says No source to compare with.
Matches sourceQuote
MongoDB documents that client operations enter the diagnostic log when they exceed the slow-operation threshold or when command verbosity is at least one.
The cited source says the same thing.
The article says “documents that client operations enter the diagnostic log when they exceed the slow-operation threshold or when command verbosity is at least one”
The source says “Client operations (such as queries) appear in the log if their duration exceeds the slow operation threshold or when the log verbosity level is at least 1”
Source cited by the article: mongodb.com/docs/v8.0/reference/log-messages
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.