How severe is CVE-2026-4202?

No CVSS score has been assigned to CVE-2026-4202 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-4202?

CVE-2026-4202 affects the following packages: ayacoo/redirect-tab (Packagist), ayacoo/redirect-tab (Packagist), ayacoo/redirect-tab (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-4202?

Update ayacoo/redirect-tab to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4202 is resolved across your whole dependency graph.

How do I detect CVE-2026-4202 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ayacoo/redirect-tab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-4202 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-4202 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-4202 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-4202?

CVE-2026-4202 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-4202?

CVE-2026-4202 is classified as Information Exposure (CWE-200), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-4202 published, and has it been updated?

CVE-2026-4202 was published on March 17, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-4202 — redirect-tab

Fix: ayacoo/redirect_tab@085f4cb

CVE-2026-4202 is a Information Exposure vulnerability in ayacoo/redirect-tab. A fix is available for ayacoo/redirect-tab — see the affected versions and patch details below.

Broken Access Control in extension "Redirect Tab"

Also known asGHSA-755r-r738-mjgp

Published

Mar 17, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-4202.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk-0.10%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐘ayacoo/redirect-tab🐘ayacoo/redirect-tab🐘ayacoo/redirect-tab

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The extension fails to verify, if an authenticated user has permissions to access to redirects resulting in exposure of redirect records when editing a page.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ayacoo/redirect-tab`	all versions	2.1.2`composer require ayacoo/redirect-tab:^2.1.2`
🐘Packagist	`ayacoo/redirect-tab`	≥ 3.0.0&&< 3.1.7	3.1.7`composer require ayacoo/redirect-tab:^3.1.7`
🐘Packagist	`ayacoo/redirect-tab`	≥ 4.0.0&&< 4.0.5	4.0.5`composer require ayacoo/redirect-tab:^4.0.5`

Affected Products

1 product · 3 configurations

Application

redirect tabayacoo

≥ 4.0.0 && < 4.0.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ayacoo/redirect-tab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ayacoo/redirect-tab to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4202 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

The extension fails to verify, if an authenticated user has permissions to access to redirects resulting in exposure of redirect records when editing a page.

O3 Security · Impact-Aware SCA

Is CVE-2026-4202 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works