学术圈不眠夜啊。 事情是这样的。 各大计算机顶会不都是双盲评审嘛，对于论文作者们而言，并不知道给自己打分的审稿人都是谁。 但就在昨个晚上，一个Bug突然疯传：只要输入特定字段到一个API链接，系统就会把审稿人的个人信息一股脑全部吐出来，包括姓名、邮箱、单位…… 并且不限于某个顶会，而是用了OpenReview的全中招了。 好家伙，约等于官方系统直接成了"人肉"平台了。 事情迅速发酵，最先被发现出问题的ICLR 2026赶忙po出声明： 2025年11月27日，ICLR发现了一个软件漏洞，这个漏洞泄露了作者、审稿人和领域主席的姓名，并影响了所有托管在OpenReview上的会议。 我们感谢OpenReview团队迅速修复了该问题。任何对泄露信息的利用和分享，都违反了ICLR行为准则，将立即导致所有投稿被拒，还会面临 ICLR的多年期禁入惩罚。如果有任何作者或审稿人联系、威胁或贿赂您，请立即向program-chairs@iclr.cc报告。 万万没想到，一个系统级大Bug，直接把ICLR、NeurIPS、ACL……各大顶会所有审稿人通通"开盒"了。 声明中强调了对人肉搜索的0容忍，但情况是，Bug虽然已经修复， ...

Core Points - A significant bug in the OpenReview system has exposed the identities of reviewers for major computer science conferences, undermining the double-blind review process [2][4][19] - The bug was reported on November 27, 2015, and was fixed within an hour, but the damage had already been done as reviewer information was harvested [6][10][12] - The incident has sparked discussions about the integrity of the peer review process and the potential need to reassess the double-blind review system [21][25] Group 1 - The bug allowed anyone to retrieve personal information of reviewers by inputting specific fields into an API link, affecting all conferences hosted on OpenReview [4][5][8] - ICLR 2026 issued a statement condemning the misuse of leaked information and warned of severe consequences for any attempts to exploit the data [6][8][13] - The incident has led to a surge of posts from authors identifying their reviewers, raising concerns about the repercussions for the peer review community [14][19][22] Group 2 - The OpenReview team is currently analyzing API call logs to determine the extent of the data breach and identify accounts that accessed sensitive information [12] - The event has prompted calls for accountability among reviewers, with some suggesting that irresponsible reviewers should lose their anonymity [24][25] - The academic community is urged to reflect on the vulnerabilities of the current review system and the potential for reform [20][21]