Skip to main content
VulnerabilityPublished Updated

CVE-2024-51463: IBM · Server-Side Request Forgery (SSRF)

Affects IBMSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 21 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by IBM Corporation

    , 54 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    IBMi Navigator 7.5 - Server Side Request Forgery (SSRF)

    , 115 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMAffected
  • =7.3
  • =7.4
  • =7.5
Fixed in–

AI-suggested

  1. Implement strict access controls on IBM i systems to limit authenticated user privileges to only those necessary, reducing the risk of misuse.
  2. Apply network segmentation to isolate IBM i systems from sensitive internal services, minimizing the impact of SSRF-induced requests.
  3. Monitor outbound traffic from IBM i systems for unusual or unauthorized requests, using intrusion detection systems or network monitoring tools.
  4. Enforce strong authentication mechanisms and regularly audit user accounts to prevent credential compromise.
  5. Restrict the IBM i system’s ability to initiate network connections to only trusted destinations via firewall rules or host-based controls.
  6. Stay informed about IBM’s security advisories and apply patches promptly once available.
  7. Conduct regular security assessments and penetration tests focusing on SSRF and related vulnerabilities within the IBM i environment.
  8. Educate system administrators about SSRF risks and encourage vigilance for suspicious system behavior or logs.

Description

IBM i 7.3, 7.4, and 7.5 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

References

Community reviews

Loading reviews…