CVE-2026-49262 Aimeos Pagible CMS vulnerable to Server Side Request Forgery (SSRF) via DNS rebinding in admin proxy

Low 3.0 Published Updated

Attackers can exploit a race condition in the admin proxy to perform Server-Side Request Forgery, accessing internal network resources and cloud metadata.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-49262?

CVE-2026-49262 is a low-severity server-side request forgery vulnerability in aimeos pagible, published on 12 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

In the Aimeos Pagible content management system prior to version 0.10.4, the administrative proxy route (`cmsproxy`) is vulnerable to a Server-Side Request Forgery (SSRF) attack via DNS Rebinding. A Time-of-Check to Time-of-Use (TOCTOU) race condition exists between the URL validation phase and the actual HTTP request phase, allowing attackers to access internal network resources and cloud metadata endpoints. Version 0.10.4 fixes the issue.

Weakness: CWE-918, CWE-367

Which versions are affected by CVE-2026-49262?

2 open source packages ship an affected version, including aimeos/pagible.

PackageAffectedFixed in
aimeos/pagible PackagistAll versions0.10.4
aimeos/pagible PackagistAll versions0.10.4

How do I fix CVE-2026-49262?

Upgrade aimeos/pagible to 0.10.4 or later.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-49262 being exploited?

There is no known exploitation of CVE-2026-49262 in the wild and no public exploit code.

Sources

Also known as GHSA-mmj8-wcvw-6789.

Is CVE-2026-49262 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free