Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac4aBrA6ssztvsrp@256bit.org>
Date: Thu, 2 Apr 2026 09:25:58 +0200
From: Christian Brabandt <cb@...bit.org>
To: oss-security@...ts.openwall.com
Subject: Re: [vim-security] Vim tabpanel modeline escape
 affects Vim < 9.2.0272


On Mo, 30 Mär 2026, Christian Brabandt wrote:

> Vim tabpanel modeline escape affects Vim < 9.2.0272
> ===================================================
> Date: 30.03.2026
> Severity: High
> CVE: *not yet assigned*

Sorry for being potentially off-topic, but I am wondering if I am doing 
something wrong here. Did anybody request a CVE for this? I got a 
notification from Github Support (after 10 hours or so) that they cannot 
assign a CVE for this, as there was already one assigned.

I typically hit the *Request CVE* button before I publish an advisory 
and send out the notifications, and usually github assigns those pretty 
fast, but not this time.

Does anybody here know how this works? Or did I do something wrong?

Best,
Christian
-- 
Frauen vereinfachen unseren Schmerz, verdoppeln unsere Freude und
verdreifachen unsere Ausgaben.
		-- James Saunders

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.