CVE-2026-49262

LOWPre-NVD 3.03.0
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
3.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.0
EG Score
3.0(medium)
EG Risk
14(Track)
EG Risk 14/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity30% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 26, 2026

Last Modified

September 9, 2026

Vendor Advisories for CVE-2026-49262(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
aimeos/pagible0.10.0 ... 0.9.4 (29 versions)0.10.4

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-09 22:59 UTCEG score recompute
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:51 UTCEG score recompute
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-31 01:50 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 22:53 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 09:20 UTCEG score recompute
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 23:30 UTCEG score recompute
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 11 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 19:36 UTCEG score recompute
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-12 16:36 UTCEG score recompute
  7. 2026-08-12 15:27 UTCEG score recompute
  8. 2026-08-01 20:24 UTCEG score recompute
  9. 2026-07-26 14:29 UTCEG score recompute
  10. 2026-07-23 03:18 UTCEG score recompute
  11. 2026-06-26 22:38 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49262?
CVE-2026-49262 is a low vulnerability published on June 26, 2026. 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…
When was CVE-2026-49262 disclosed?
CVE-2026-49262 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49262 actively exploited?
CVE-2026-49262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-49262?
CVE-2026-49262 has a CVSS v3 base score of 3.0 (NVD).
How do I remediate CVE-2026-49262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49262, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49262

Explore →

Is Your Infrastructure Affected by CVE-2026-49262?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.