Edition of Wednesday 18 November 2026

Account Takeover in Phase Two's Keycloak Organizations Extension

Comments on “Account Takeover in Phase Two's Keycloak Organizations Extension”

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

Ferment.fan reports an account-takeover flaw in Phase Two's open-source keycloak-orgs extension for Keycloak. The domain verifier ran after first broker login had already created a user and federated identity link, so a rejected out-of-domain login left both behind. With the default FORCE sync, a later in-domain login could then overwrite the victim's email and obtain a session. Phase Two added a pre-creation check in version 0.199. Existing links need auditing. Most details come from the authors' own local reproduction and disclosure account.

Read the original at ferment.fan. 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. 4 of 142 with a score of 0.73. The panel rated it highest on new information (0.94) and technical depth (0.90), lowest on audience breadth (0.40).

AI judgeJudge 2claude-haiku-5-5
Detailed, reproduced authentication flaw in Keycloak SSO extension with clear root cause and fix; strongly security-focused, practical for builders running identity infrastructure, moderately niche audience.
AI judgeJudge 3gpt-5.6-luna
A well-reproduced Keycloak extension vulnerability demonstrates account takeover through persistent identity-link creation before validation, explains the flow-ordering root cause, and provides concrete affected versions, remediation, and audit guidance.

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.73total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.63
  • Reader interest0.84
  • Audience breadth0.40
  • Practical relevance0.86
  • Substantiated0.90
  • Technical depth0.90
  • New information0.94
  • Counts against: Promotional0.04
  • Counts against: Overclaim0.13

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.570.550.780.630.23+0.24+0.152
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.780.800.940.840.16+0.26+0.218
Audience breadthHow many people who build technology does it concern?0.370.400.420.400.05+0.13+0.052
Practical relevanceHow useful is it to someone who builds software or tech products?0.890.800.880.860.09+0.22+0.188
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.940.850.910.900.09+0.05+0.045
Technical depthHow technically substantive is it?1.000.850.860.900.15+0.05+0.045
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.890.950.980.940.09+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.040.050.020.040.03−0.19−0.007
OverclaimDo the headline or conclusions claim more than the body supports?0.160.150.080.130.08−0.11−0.014
Sum of contributions+0.727
Claim-check penalty0.000
Total, as published0.727

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

Claim check

Claim check: 1 matches source · 4 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 checkCausal conclusion

    The post-broker ext-auth-org-id-verifier was introduced in keycloak-orgs PR #316 after the project identified the adversarial-IdP case in issue #312.

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

    The article says

    “The post-broker ext-auth-org-id-verifier was introduced in keycloak-orgs #316 after the project had identified the adversarial-IdP case in issue #312”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/p2-inc/keycloak-orgs/pull/316

  2. No source givenNumber

    The default synchronization mode for keycloak-orgs IdPs is FORCE, which replaces local attributes such as email, username, first name and last name with IdP claims on every sign-in.

    The article gives no link or citation for it.

    The article says

    “The default for keycloak-orgs IdPs is FORCE, which replaces local attributes—including email, username, first name, and last name—with claims from the IdP whenever that IdP user signs in”

    The source says

    No source to compare with.

  3. No source givenCausal conclusion

    In the authors' local reproduction, the verifier rejected an out-of-domain login, but the Admin API showed the user victim@external.example and a federated identity link had still been created.

    The article gives no link or citation for it.

    The article says

    “But the Keycloak Admin API showed that victim@external.example had been created anyway, with a federated identity link from the mock IdP to that user”

    The source says

    No source to compare with.

  4. No source givenDate

    The authors reported the finding to Phase Two on November 16, 2026, and Phase Two's CEO replied within hours.

    The article gives no link or citation for it.

    The article says

    “We reported the finding to Phase Two on November 16, 2026, with a reproduction and a proposed user-less, first-broker-login domain check”

    The source says

    No source to compare with.

  5. Couldn’t checkVersion

    The fix was shipped in the Phase Two container image quay.io/phasetwo/phasetwo-keycloak:26.8.2.1794862673.

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

    The article says

    “shipped it in quay.io/phasetwo/phasetwo-keycloak:26.8.2.1794862673”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/p2-inc/phasetwo-containers/pull/212

  6. Matches sourceVersion

    The fix adds ext-auth-org-domain-fbl-verifier, a user-less authenticator in the first broker-login flow that rejects an out-of-domain brokered email before a user or link is created.

    The cited source says the same thing.

    The article says

    “The fix adds ext-auth-org-domain-fbl-verifier, a user-less authenticator placed in the first broker-login flow after idp-review-profile and before idp-create-user-if-unique”

    The source says

    “New user-less first-broker-login authenticator **`ext-auth-org-domain-fbl-verifier`** that checks the brokered email domain against the organization(s) that own the IdP, **before** `idp-create-user-if-unique”

    Source cited by the article: github.com/p2-inc/keycloak-orgs/pull/527

  7. Couldn’t checkVersion

    Keycloak-orgs 0.199 is the release that includes the remediation; the advisory metadata lists affected versions as <0.197 while its description says 0.197 was also affected.

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

    The article says

    “The advisory metadata currently lists affected versions as <0.197, while its description states that 0.197 was also affected; 0.199 is the release that includes the remediation”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/p2-inc/keycloak-orgs/security/advisories/GHSA-gvcc-4vw2-6wvr

  8. No source givenCausal conclusion

    Changing the IdP sync mode from FORCE to IMPORT is not a sufficient mitigation because the defect is link creation before domain validation.

    The article gives no link or citation for it.

    The article says

    “Changing the IdP sync mode from FORCE to IMPORT is not a sufficient mitigation”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 18 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 “Account Takeover in Phase Two's Keycloak Organizations Extension”

More on Rubric

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