VDB
RHSA-2025:19472
RHSA-2025:19472
PUBLISHED
CVSS 8.100000381469727 HIGH
Record from OSV · Published November 3, 2025
Red Hat Security Advisory: libssh security update
Risk scores
CVSS 3.1
8.100000381469727
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat:rhel_e4s:9.0::appstream | libssh-config | 0, 0 |
| Red Hat:rhel_e4s:9.0::baseos | libssh-debugsource | 0, 0 |
| Red Hat:rhel_e4s:9.0::appstream | libssh | 0, 0 |
| Red Hat:rhel_e4s:9.0::baseos | libssh | 0, 0 |
| Red Hat:rhel_e4s:9.0::appstream | libssh-devel | 0, 0 |
| Red Hat:rhel_e4s:9.0::appstream | libssh-debuginfo | 0, 0 |
| Red Hat:rhel_e4s:9.0::appstream | libssh-debugsource | 0, 0 |
| Red Hat:rhel_e4s:9.0::baseos | libssh-config | 0, 0 |
| Red Hat:rhel_e4s:9.0::baseos | libssh-devel | 0, 0 |
| Red Hat:rhel_e4s:9.0::baseos | libssh-debuginfo | 0, 0 |
Timeline
- Nov 3, 2025 CVE Published
- Mar 18, 2026 CVE Updated
- May 1, 2026 Distribution Patch (2 in total, the first dated here)
- May 1, 2026 Security Advisory (2 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln RHSA-2025:19472
vulnetix vdb fixes RHSA-2025:19472
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/RHSA-2025%3A19472/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://access.redhat.com/errata/RHSA-2025:19472 advisory
- https://access.redhat.com/security/updates/classification/#moderate article
- https://bugzilla.redhat.com/show_bug.cgi?id=2369131 report
- https://www.cve.org/CVERecord?id=CVE-2025-5318 advisory
- https://nvd.nist.gov/vuln/detail/CVE-2025-5318 advisory
- https://www.libssh.org/security/advisories/CVE-2025-5318.txt article
- https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_19472.json advisory
- https://access.redhat.com/security/cve/CVE-2025-5318 report