Skip to main content
Mallory
UnratedVulnerability

CVE-2026-124846: PHP2Shell: Remote Code Execution via Out-of-Memory Corruption in Bizerba RDM

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-124846CWE-416

An out-of-memory corruption/use-after-free vulnerability affecting the Bizerba RDM web service can allow an unauthenticated remote attacker to execute arbitrary code through specially crafted requests. The affected component is the PHP runtime used by RDM; the vulnerable function and complete affected-version range are not established. The vendor advisory identifies CVE-2026-124846 in its heading but references CVE-2026-109618 and CVE-2026-109619 in its description, leaving the relationship between these identifiers unresolved.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can execute arbitrary code with the privileges of the web server or PHP process, enabling access to, modification of, or deletion of data and disruption of the RDM service. The advisory assigns CVSS v3.1 9.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).

Remediation

Patch, then assume compromise.

Update the PHP runtime used by RDM to version 8.2.35, as explicitly recommended by the vendor. The product-status table uses ambiguous version labels and does not reliably establish the complete affected or fixed version ranges.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-124846 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-124846 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-124846?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-124846.
Is there a patch for CVE-2026-124846?
Update the PHP runtime used by RDM to version 8.2.35, as explicitly recommended by the vendor. The product-status table uses ambiguous version labels and does not reliably establish the complete affected or fixed version ranges.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.