The last 5 days have been a bit wild for the GCVE.eu initiative.

What started as steady work suddenly picked up real momentum:

• The public GCVE.eu database instance - https://db.gcve.eu/ - caught the attention of the media, sparking discussions well beyond our usual circles

• We published updates to the GCVE KEV Assertion Standard Format (BCP-07), refining how known-exploited information can be asserted and shared

• Vulnerability-Lookup 2.21.0 was released, bringing improvements aligned with the GCVE ecosystem

• We received a lot of valuable feedback especially on the specs, the tooling, and the overall direction

• New GNAs joined the GCVE directory, and new contributors stepped in to help shape both the specifications and the software

Seeing this level of engagement, critique, and contribution in such a short time is incredibly motivating. It reinforces why an open, decentralized, and collaborative approach to vulnerability identification and sharing matters.

Huge thanks to everyone who tested, commented, challenged assumptions, wrote code, improved text, or simply helped spread the word. This is very much a community effort and it’s only getting started. 💙

#GCVE #OpenSource #VulnerabilityManagement #CyberSecurity #Standards #Community

Don't hesitate to follow us at GCVE-EU - @gcve

@circl

GCVE BCP - https://gcve.eu/bcp/
GCVE DB - https://db.gcve.eu/recent
Vulnerability-Lookup - https://github.com/vulnerability-lookup/vulnerability-lookup

The last 5 days have been a bit wild for the GCVE.eu initiative.

What started as steady work suddenly picked up real momentum:

• The public GCVE.eu database instance - https://db.gcve.eu/ - caught the attention of the media, sparking discussions well beyond our usual circles

• We published updates to the GCVE KEV Assertion Standard Format (BCP-07), refining how known-exploited information can be asserted and shared

• Vulnerability-Lookup 2.21.0 was released, bringing improvements aligned with the GCVE ecosystem

• We received a lot of valuable feedback especially on the specs, the tooling, and the overall direction

• New GNAs joined the GCVE directory, and new contributors stepped in to help shape both the specifications and the software

Seeing this level of engagement, critique, and contribution in such a short time is incredibly motivating. It reinforces why an open, decentralized, and collaborative approach to vulnerability identification and sharing matters.

Huge thanks to everyone who tested, commented, challenged assumptions, wrote code, improved text, or simply helped spread the word. This is very much a community effort and it’s only getting started. 💙

#GCVE #OpenSource #VulnerabilityManagement #CyberSecurity #Standards #Community

Don't hesitate to follow us at GCVE-EU - @gcve

@circl

GCVE BCP - https://gcve.eu/bcp/
GCVE DB - https://db.gcve.eu/recent
Vulnerability-Lookup - https://github.com/vulnerability-lookup/vulnerability-lookup

Luxembourg, 2026/01/07 - The GCVE initiative is proud to announce the public launch of db.gcve.eu , a new open and freely accessible vulnerability advisory database. The platform aggregates and correlates vulnerability information from more than 25 public sources, including GCVE GNA (Numbering Authority) sources and other established vulnerability databases.

🔗 For more details - https://gcve.eu/2026/01/07/gcve-db-announce/
🔗 https://db.gcve.eu/

#cve #gcve #cybersecurity #vulnerabilitymanagement #vulnerability

Luxembourg, 2026/01/07 - The GCVE initiative is proud to announce the public launch of db.gcve.eu , a new open and freely accessible vulnerability advisory database. The platform aggregates and correlates vulnerability information from more than 25 public sources, including GCVE GNA (Numbering Authority) sources and other established vulnerability databases.

🔗 For more details - https://gcve.eu/2026/01/07/gcve-db-announce/
🔗 https://db.gcve.eu/

#cve #gcve #cybersecurity #vulnerabilitymanagement #vulnerability