home.social

#gcve — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gcve, aggregated by home.social.

fetched live
  1. 📊 Vulnerability Report — July 2026 is out

    vulnerability-lookup.org/2026/

    A record of published CVEs (+23% over June) and 61,263 sightings.

    4 SharePoint flaws in CISA KEV in 4 weeks, a chained WordPress core pair topping the sightings, and a wave of Joomla extensions.

    We put 5 KEV catalogs side by side: 65 vulnerabilities entered at least one in July — watching only CISA would have missed nearly half.

    #CTI #KEV #VulnerabilityLookup #VulnerabilityReport #GCVE #CVE #OpenSource #CyberSecurity

  2. 🚀 Vulnerability-Lookup 6.0.0 is out!

    🔔 Webhook notifications — push your product reports to any HTTPS endpoint (chat, SIEM, ticketing), with a configurable payload and a strict outbound policy.

    📈 Local exploit hazard — new API endpoints, hazard-ordered reports, and daily standing exposure alerts.

    👥 A searchable vulnerability credits index
    🧭 SSVC v2.0 decisions on the CVE page

    👉 vulnerability-lookup.org/2026/

    #CVE #EPSS #KEV #GCVE #OpenSource #OpenData #Software #Community #AI #CyberSecurity

  3. vulnerability-lookup 6.0 will be released this week with many (really, many!) new features.

    One of the smaller, but important, additions is support for multiple SSVC views alongside CVSS. When SSVC information is available from an ADP (such as CISA) , or from additional sources such as GCVE, it is now displayed by default.

    This allows users to more easily compare the different severity and prioritization assessments associated with a vulnerability.

    The CIRCL vulnerability-lookup instance is running the pre-release of 6.0 -
    vulnerability.circl.lu/vuln/cv

    #cve #gcve #opensource #vulnerabilitylookup #opendata #vulnerabilitymanagement #cyberecurity #ssvc

    @gcve
    @circl

  4. From a research paper to running open-source code in just a few days.

    We (with @cedric) have been experimenting in Vulnerability-Lookup with the concept of Local Exploit Hazard, based on the recent research paper “Modeling Local Exploit Hazard — A Bayesian Framework for Quantifying Exploit Risk and Operational Efficiency” by Stephen Shaffer and Laura Cristiana Voicu.

    The idea addresses an important question in vulnerability management:

    Not simply “How dangerous is this vulnerability globally?” but “How much exploitation risk does this vulnerability represent in my environment?”

    Instead of introducing yet another static vulnerability score, the model starts from exploit likelihood such as EPSS and combines it with local security controls, CVSS attack vectors, vulnerability age and KEV policy to estimate an exploitation hazard.

    We implemented an experimental version in Vulnerability-Lookup and connected it directly to operational workflows.

    For the full details: vulnerability-lookup.org/2026/

    #cve #gcve #vulnerabilitymanagement #vulnerability #opensource #opendata

    @circl

  5. NatJack: A New Attack Class Against Network Infrastructure Devices

    All CVEs tracked in a single bundle to see all the allocating.

    #cve #gcve #natjack

    vulnerability.circl.lu/bundle/

  6. Working on a first super beta implementation of @gcve BCP-11 "Community-Proposed Updates to Existing CVE Records"

    To validate if the BCP-11 can be published.

    #cve #gcve #vulnerability #opensource #opendata

    Discussions discourse.ossbase.org/t/gcve-b

  7. Pretty cool idea from @nyanbinary - a bot to analyse fucked up references from the CVE records.

    @fuckeduprefs_bot

    Maybe we could imagine an archive bot at the same time to ensure that the references don't get lost. Just like archive.org or similar. Maybe something for @gcve to look into.

    #cve #vulnerability #gcve

  8. Sightings have long been a major topic of discussion in the CTI community, particularly in the field of vulnerability management. We have now published a GCVE BCP to standardise the format that has been implemented, tested and used operationally in Vulnerability-Lookup for some time.

    Thanks to everyone (Cédric Bonhomme, Éireann Leverett, Andras Iklody, Sami Mokaddem and many more) who participated in discussions and worked on the implementation details of sightings over the past several years. These efforts had a strong focus on practical implementation, while BCP-12 specifically addresses sightings in the context of vulnerability management.

    BCP-12 is still a draft open for review, but it already provides a strong foundation for existing implementations.

    gcve.eu/2026/08/01/gcve-bcp-12

    #cve #cra #gcve #vulnerabilitymanagement #cybersecurity #openstandard

  9. A new version of the BCP-11 "Community Contribution Fragments for Existing CVE Records" proposal has been published.

    discourse.ossbase.org/t/gcve-b

    This new version is a major refactoring of the originally proposed format.

    Feel free to comment, update or propose changes.

    An implementation will follow when the BCP-11 reach a more stable state.

    #gcve #cve #cybersecurity #vulnerabilitymanagement

    @gcve

  10. The GCVE Lab is an open space for experimenting with new ideas, tools, formats, and services related to the Global CVE Allocation System initiative.

    The lab allows the GCVE community to explore promising concepts without immediately imposing the stability, compatibility, and operational requirements expected from the core GCVE infrastructure.

    Open to comments/ideas.

    #gcve #cve #cybersecurity

    discourse.ossbase.org/t/gcve-l

    gcve.eu

    @[email protected] @[email protected]

  11. 282,000+ VEX records are now in Vulnerability-Lookup 🎉

    🔎 vulnerability.circl.lu/vex

    SUSE just joined Red Hat and Microsoft as a VEX source — so from any CVE you can see whether a vendor says a product is affected, fixed, or not affected.

    VEX statements are attached directly to each vulnerability and available via the open API.

    🧑‍💻 github.com/vulnerability-looku

    #VEX #CSAF #VulnerabilityManagement #OpenSource #InfoSec #GCVE #CVE #CYberSecurity #Vulnerability

  12. You can now browse VEX statements in Vulnerability-Lookup!

    The new VEX page lets you explore 220k+ vendor VEX records (Red Hat, Microsoft MSRC, more coming), filter by source, search by CVE ID or title, see product statuses at a glance (fixed, known affected, not affected, under investigation) and pivot straight to the related vulnerability.

    🔎 vulnerability.circl.lu/vex/
    🧩 API: vulnerability.circl.lu/api/vex/

    #VEX #VulnerabilityLookup #CVE #GCVE #OpenSource #CyberSecurity

  13. 📦 gcve 0.12.1 is out — a small maintenance release with updated dependencies.

    gcve is a Python client and CLI for the Global CVE Allocation System (GCVE), a decentralized approach to vulnerability identification where multiple GCVE Numbering Authorities can allocate IDs independently, with a cryptographically signed registry.

    🔗 gcve.eu
    🐍 pipx install gcve
    💻 github.com/gcve-eu/gcve

  14. 📦 gcve 0.12.1 is out — a small maintenance release with updated dependencies.

    gcve is a Python client and CLI for the Global CVE Allocation System (GCVE), a decentralized approach to vulnerability identification where multiple GCVE Numbering Authorities can allocate IDs independently, with a cryptographically signed registry.

    🔗 gcve.eu
    🐍 pipx install gcve
    💻 github.com/gcve-eu/gcve

    #GCVE #CVE #VulnerabilityManagement #CyberSecurity #Python #OpenSource

  15. We just released cve-search v6.0.1 - it is a security and maintenance release. All users are strongly encouraged to upgrade.

    Thanks to @oh2fih for the remediation fix and release support. Thanks to George Chen for the report about the security vulnerability.

    #cve #gcve #cybersecurity

    🔗 github.com/cve-search/cve-sear

  16. A new KEV Catalog built from real-world exploitation data !

    vulnerability.circl.lu/known-e

    We are excited to share the result of a fruitful collaboration with @shadowserver: a new Known Exploited Vulnerabilities (KEV) Catalog (BCP-07 compliant) built directly from their global honeypot telemetry.

    #ShadowServer #KEV #GCVE #Vulnerability #VulnerabilityManagement #Decentralization #Fragmentation

  17. Improving the CPE editor for the GCVE initiative: clearer API behavior, better performance, and many other enhancements. This will be released in version 1.1 and the improvements are already in the online version.

    🌍️ Online version cpe.gcve.eu/
    :github: github.com/gcve-eu/cpe-editor

    If you want to improve the CPE dataset, you can make proposal online.

    Thanks to all the users who provided feedback for improvements @righel @cedric @jgamblin

    @gcve

    #gcve #cpe #cve #vulnerability #vulnerabilitymanagement #opensource #opendata

  18. 🎉 Vulnerability-Lookup 5.2.0 is out!

    This release comes with plenty of improvements and is the result of many expensive AI tokens consumed by Claude Code under the supervision of its human orchestrator.

    Curious? Have a look at the release notes:

    vulnerability-lookup.org/2026/

    #AI #Orchestration #Vulnerability #OpenSource #GCVE #CVE #CVD #GNA

  19. The idea from @bagder is so interesting that it gave me the idea to extend the "GCVE-BCP-02 - Practical Guide to Vulnerability Handling and Disclosure" with "Temporary Closure of Vulnerability Intake Windows"

    #gcve #cve #vulnerabilitymanagement #vulnerability #opensource #cybersecurity

    🔗 Proposal discourse.ossbase.org/t/tempor
    🔗 Original BCP-02 gcve.eu/bcp/gcve-bcp-02/

  20. 📢 Vulnerability-Lookup 5.1.0 released!

    New CNA Publication Service: publish vulnerabilities from your local instance (GCVE) directly to the official CVE Program via MITRE's CVE Services — one record, two identifiers, no duplication, with built-in moderation as part of CVD.

    Plus: exploited-CVE ratio statistics, CSAF advisories in full-text search, and UI improvements.

    vulnerability-lookup.org/2026/

    #CyberSecurity #OpenSource #CVD #GCVE #CNA #CVE

  21. Playing with CSAF 2.1 CSD02 and GCVE extensions.

    discourse.ossbase.org/t/csaf-a

    I think more and more that having GCVE extension on all vulnerability standard format makes much more sense nowadays.

    #gcve #cve #csaf

    @gcve