home.social

#gcve β€” Public Fediverse posts

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

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. πŸ“¦ 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

  12. πŸ“¦ 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

  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

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

  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. πŸ“¦ 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

  16. πŸ“¦ 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

  17. πŸ“¦ 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

  18. πŸ“¦ 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

  19. πŸ“¦ 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. 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

  25. 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

  26. 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

  27. 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

  28. 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

  29. 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

  30. 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

  31. 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

  32. 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

  33. 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

  34. 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

  35. πŸŽ‰ 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

  36. πŸŽ‰ 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

  37. πŸŽ‰ 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

  38. πŸŽ‰ 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

  39. πŸŽ‰ 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

  40. 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/

  41. 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/

  42. 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/

  43. 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/

  44. 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/