Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-18745 – Unauthenticated Remote Code Execution via PHP Object Injection – ILIAS 9.0–9.21, 10

Be the first to know when new zero-days emerge:

Summary

CVE-2026-18745 was reserved on 2026-08-03 and published on 2026-09-04, but it was rejected/withdrawn by its CVE Numbering Authority (VulnCheck) on the same day it was published (2026-09-04). The official CVE record contains no vulnerability description, no CVSS score, no affected product/version data, and no references — only a rejection notice.

Technical details

  • No technical details are available: the authoritative CVE record (CVE List V5) contains only cveMetadata and a rejectedReasons block.
  • The rejection reason given is the standard boilerplate: "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
  • No CNA container with a description, CWE, affected products, or CVSS metrics was ever published for this ID.
  • Third-party aggregator sites describe this ID as an "ILIAS unauthenticated PHP object injection / deserialization" issue, but this description does not appear in any authoritative source (MITRE CVE List, NVD, or an ILIAS vendor advisory) and cannot be verified.

Affected software

  • None confirmed. No affected product or version range is published in the authoritative record for this CVE ID.

Severity

  • No CVSS score or vector is published in the authoritative CVE record for this ID. (A CVSS 9.3 score was supplied as prior context but could not be verified against any primary source and is not reproduced here.)

Mitigation and recommended actions

  • No patch or mitigation guidance can be issued against this specific CVE ID, since it carries no verified vulnerability description.
  • Security teams tracking ILIAS deployments should monitor official ILIAS security advisories and the CVE record directly for a possible re-publication under a corrected or new CVE ID, and should not take remediation action based on this rejected ID alone.
  • General hygiene: keep ILIAS installations on vendor-supported, currently patched releases and monitor the official ILIAS release/security channels for advisories.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge