https://github.com/estaji/check-cves

Collection of codes to verify servers, applications and infrastructure immunity against specific CVEs.
https://github.com/estaji/check-cves

security security-tools vulnerability-detection vulnerability-scanner vulnerability-scanners

Last synced: 30 days ago
JSON representation

Collection of codes to verify servers, applications and infrastructure immunity against specific CVEs.

• Host: GitHub
• URL: https://github.com/estaji/check-cves
• Owner: estaji
• License: mit
• Created: 2025-04-06T07:32:56.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2026-05-17T09:14:53.000Z (2 months ago)
• Last Synced: 2026-05-17T11:25:34.833Z (2 months ago)
• Topics: security, security-tools, vulnerability-detection, vulnerability-scanner, vulnerability-scanners
• Homepage:
• Size: 14.6 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# About

Collection of codes to verify servers, applications and infrastructure immunity against specific CVEs.

# How

Use instruction in each CVE directory to check whether your servers or apps are vulnerable.

These codes are helpful when you have many servers and do not want to check on each one manually.

## 🛡️ Covered CVEs

Below is the current list of vulnerabilities supported by this verification suite:

| CVE ID | Impacted Component | Description & Check Summary |

| :--- | :--- | :--- |

| **CVE-2026-42945** | NGINX | A vulnerability in the ngx_http_rewrite_module module. |

| **CVE-2025-26465** | OpenSSH | It could enable adversaries to launch machine-in-the-middle/man-in-the-middle (MitM) or denial-of-service (DoS) attacks. |

| **CVE-2025-26466** | OpenSSH | It could enable adversaries to launch machine-in-the-middle/man-in-the-middle (MitM) or denial-of-service (DoS) attacks. |

# Contribution

Contributions are highly welcomed! Whether you are fixing a bug, improving documentation, or adding automated checks for a new CVE, your help makes infrastructure safer for everyone.

How to Contribute

1. Fork the repository.

2. Create a branch for your feature or CVE check (git checkout -b cve-202X-XXXX-verification).

3. Implement your script following the project standard (return exit code 0 if safe, non-zero if vulnerable).

4. Update the table in this README.md with your CVE details and a brief summary.

5. Open a Pull Request explaining your testing methodology.