Trendoday

Azure's Weakest Link – Five Full Cross-Tenant Compromises

57 comments

  • Points258
  • Comments48
#5Rank now 1
#4Peak rank
2Days on list
262Score · 7d
Oct 30, 2026First seen
Rank · 7 days

On Hacker News

Points
258
Comments
48
Submitted by
swq115
Posted
Oct 30, 2026
Site
binarysecurity.no

Story details from Hacker News ↗ · linked article on binarysecurity.no.

Trending history

Azure's Weakest Link – Five Full Cross-Tenant Compromises was first seen on Hacker News · Front page on Oct 30, 2026. Since then it has appeared in 79 checks on 2 different days. Its best position was #4 of 30, reached on Oct 30, 18:52 UTC. It is #5 right now, holding steady at #5 over the last 6 checks. The same link also trended on Lobsters, which raises its cross-platform score.

Rank history

Position on Hacker News · Front page at every check (lower is better).

#1#11#20#30 12:0716:5921:5202:4407:37 Oct 30, 12:07 UTC · #29Oct 30, 12:22 UTC · #28Oct 30, 12:37 UTC · #28Oct 30, 12:52 UTC · #23Oct 30, 13:07 UTC · #22Oct 30, 13:22 UTC · #20Oct 30, 13:37 UTC · #16Oct 30, 13:52 UTC · #17Oct 30, 14:07 UTC · #17Oct 30, 14:22 UTC · #16Oct 30, 14:37 UTC · #14Oct 30, 14:52 UTC · #13Oct 30, 15:07 UTC · #13Oct 30, 15:22 UTC · #14Oct 30, 15:37 UTC · #14Oct 30, 15:52 UTC · #13Oct 30, 16:07 UTC · #13Oct 30, 16:22 UTC · #12Oct 30, 16:37 UTC · #11Oct 30, 16:52 UTC · #13Oct 30, 17:07 UTC · #10Oct 30, 17:22 UTC · #10Oct 30, 17:37 UTC · #9Oct 30, 17:52 UTC · #5Oct 30, 18:07 UTC · #6Oct 30, 18:22 UTC · #5Oct 30, 18:37 UTC · #5Oct 30, 18:52 UTC · #4Oct 30, 19:07 UTC · #5Oct 30, 19:22 UTC · #7Oct 30, 19:37 UTC · #6Oct 30, 19:52 UTC · #6Oct 30, 20:07 UTC · #6Oct 30, 20:22 UTC · #5Oct 30, 20:37 UTC · #4Oct 30, 20:52 UTC · #4Oct 30, 21:07 UTC · #4Oct 30, 21:22 UTC · #4Oct 30, 21:37 UTC · #4Oct 30, 21:52 UTC · #4Oct 30, 22:07 UTC · #4Oct 30, 22:22 UTC · #5Oct 30, 22:37 UTC · #5Oct 30, 22:52 UTC · #4Oct 30, 23:07 UTC · #4Oct 30, 23:22 UTC · #4Oct 30, 23:37 UTC · #4Oct 30, 23:52 UTC · #4Oct 31, 00:07 UTC · #4Oct 31, 00:22 UTC · #4Oct 31, 00:37 UTC · #4Oct 31, 00:52 UTC · #4Oct 31, 01:07 UTC · #4Oct 31, 01:22 UTC · #5Oct 31, 01:37 UTC · #5Oct 31, 01:52 UTC · #5Oct 31, 02:07 UTC · #5Oct 31, 02:22 UTC · #5Oct 31, 02:37 UTC · #5Oct 31, 02:52 UTC · #5Oct 31, 03:07 UTC · #5Oct 31, 03:22 UTC · #5Oct 31, 03:37 UTC · #5Oct 31, 03:52 UTC · #5Oct 31, 04:07 UTC · #5Oct 31, 04:22 UTC · #5Oct 31, 04:37 UTC · #5Oct 31, 04:52 UTC · #5Oct 31, 05:07 UTC · #5Oct 31, 05:22 UTC · #5Oct 31, 05:37 UTC · #5Oct 31, 05:52 UTC · #5Oct 31, 06:07 UTC · #5Oct 31, 06:22 UTC · #5Oct 31, 06:37 UTC · #4Oct 31, 06:52 UTC · #5Oct 31, 07:07 UTC · #5Oct 31, 07:22 UTC · #5Oct 31, 07:37 UTC · #5

Last 14 days

Best rank per day (UTC).

Oct 18today

Metric history

points as reported by Hacker News.

0100199302 12:0716:5921:5202:4407:37 Oct 30, 12:07 UTC · 9Oct 30, 12:22 UTC · 17Oct 30, 12:37 UTC · 25Oct 30, 12:52 UTC · 52Oct 30, 13:07 UTC · 64Oct 30, 13:22 UTC · 71Oct 30, 13:37 UTC · 88Oct 30, 13:52 UTC · 96Oct 30, 14:07 UTC · 102Oct 30, 14:22 UTC · 109Oct 30, 14:37 UTC · 120Oct 30, 14:52 UTC · 126Oct 30, 15:07 UTC · 134Oct 30, 15:22 UTC · 138Oct 30, 15:37 UTC · 147Oct 30, 15:52 UTC · 153Oct 30, 16:07 UTC · 160Oct 30, 16:22 UTC · 166Oct 30, 16:37 UTC · 171Oct 30, 16:52 UTC · 181Oct 30, 17:07 UTC · 185Oct 30, 17:22 UTC · 188Oct 30, 17:37 UTC · 192Oct 30, 17:52 UTC · 196Oct 30, 18:07 UTC · 200Oct 30, 18:22 UTC · 202Oct 30, 18:37 UTC · 202Oct 30, 18:52 UTC · 208Oct 30, 19:07 UTC · 210Oct 30, 19:22 UTC · 212Oct 30, 19:37 UTC · 214Oct 30, 19:52 UTC · 218Oct 30, 20:07 UTC · 219Oct 30, 20:22 UTC · 224Oct 30, 20:37 UTC · 226Oct 30, 20:52 UTC · 231Oct 30, 21:07 UTC · 231Oct 30, 21:22 UTC · 235Oct 30, 21:37 UTC · 238Oct 30, 21:52 UTC · 241Oct 30, 22:07 UTC · 244Oct 30, 22:22 UTC · 247Oct 30, 22:37 UTC · 250Oct 30, 22:52 UTC · 254Oct 30, 23:07 UTC · 255Oct 30, 23:22 UTC · 255Oct 30, 23:37 UTC · 255Oct 30, 23:52 UTC · 256Oct 31, 00:07 UTC · 257Oct 31, 00:22 UTC · 258Oct 31, 00:37 UTC · 260Oct 31, 00:52 UTC · 260Oct 31, 01:07 UTC · 260Oct 31, 01:22 UTC · 261Oct 31, 01:37 UTC · 262Oct 31, 01:52 UTC · 263Oct 31, 02:07 UTC · 264Oct 31, 02:22 UTC · 268Oct 31, 02:37 UTC · 271Oct 31, 02:52 UTC · 272Oct 31, 03:07 UTC · 274Oct 31, 03:22 UTC · 275Oct 31, 03:37 UTC · 278Oct 31, 03:52 UTC · 278Oct 31, 04:07 UTC · 278Oct 31, 04:22 UTC · 281Oct 31, 04:37 UTC · 281Oct 31, 04:52 UTC · 283Oct 31, 05:07 UTC · 284Oct 31, 05:22 UTC · 284Oct 31, 05:37 UTC · 286Oct 31, 05:52 UTC · 288Oct 31, 06:07 UTC · 291Oct 31, 06:22 UTC · 294Oct 31, 06:37 UTC · 296Oct 31, 06:52 UTC · 297Oct 31, 07:07 UTC · 300Oct 31, 07:22 UTC · 301Oct 31, 07:37 UTC · 302

Where it trended

From the discussion

A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.

If anyone from Microsoft security reads this, could you please do something about login.microsoftonline.com/XXX/v2.0/adminconsent? The callback you're redirecting the user to at the end of that flow is forgeable if an attacker knows an azure tenant ID of a different customer, and putting a "Never use the tenant ID…

When it comes to the amount of cross-tenant leaks Azure looks to be way ahead the competition. Makes me wonder why enterprises still flock there.

maybe we should tag submissions with dates now? [2026-10-02] beginning of curent month feels like two years ago when multiple vulns drop daily

Questions

Is Azure's Weakest Link – Five Full Cross-Tenant Compromises trending on Hacker News right now?

Yes. As of Oct 31, 07:37 UTC it is #5, holding steady at #5 over the last 6 checks.

What is the highest rank Azure's Weakest Link – Five Full Cross-Tenant Compromises reached?

#4 on Hacker News · Front page, on Oct 30, 18:52 UTC. Trendoday checks this list every 15 minutes.

How long has Azure's Weakest Link – Five Full Cross-Tenant Compromises been trending?

It was first seen on Oct 30, 2026 and has been on the list on 2 days (79 checks) since.

How much discussion did it get on Hacker News?

258 points and 48 comments; submitted by swq115 on Oct 30, 2026.