https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 17:12:49 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-328891 EUVD-2026-328891 https://cve.radiocsirt.org/vuln/euvd-2026-328891 https://cve.radiocsirt.org/vuln/fkie_cve-2026-12049 <p>Open redirect in pgAdmin 4&#39;s multi-factor authentication flow. The MFA validate and register endpoints honoured the user-supplied &#39;next&#39; query/form parameter without confirming the target pointed back inside pgAdmin, so an authenticated victim who clicked /mfa/validate?next=&lt;external&gt; -- a link typically delivered by phishing -- would be sent to an attacker-controlled host directly out of the trusted auth flow.</p> <p>The defect is a trusted-domain redirect, not a privilege bypass: the attacker gains no read/write access to pgAdmin or the victim&#39;s database, but the redirect launders the attacker&#39;s destination through pgAdmin&#39;s URL, which raises the success rate of credential-phishing follow-on against the victim.</p> <p>Fix introduces a same-origin _is_safe_redirect_url helper and gates every MFA redirect that consumes user-supplied &#39;next&#39; values through it. The helper allows only relative paths and absolute URLs whose scheme is http(s) and whose host matches the current request host; it rejects external hosts in absolute and protocol-relative form, non-http schemes (javascript:, data:, mailto:), userinfo tricks (http://localhost@attacker/), and backslash variants that some browsers normalize to forward slashes. Unsafe targets fall back to the internal browser index. A dedicated regression test exercises each accept/reject category and the original reporter PoC.</p> <p>This issue affects pgAdmin 4: from 6.0 before 9.16.</p> <p>Open redirect in pgAdmin 4&#39;s multi-factor authentication flow. The MFA validate and register endpoints honoured the user-supplied &#39;next&#39; query/form parameter without confirming the target pointed back inside pgAdmin, so an authenticated victim who clicked /mfa/validate?next=&lt;external&gt; -- a link typically delivered by phishing -- would be sent to an attacker-controlled host directly out of the trusted auth flow.</p> <p>The defect is a trusted-domain redirect, not a privilege bypass: the attacker gains no read/write access to pgAdmin or the victim&#39;s database, but the redirect launders the attacker&#39;s destination through pgAdmin&#39;s URL, which raises the success rate of credential-phishing follow-on against the victim.</p> <p>Fix introduces a same-origin _is_safe_redirect_url helper and gates every MFA redirect that consumes user-supplied &#39;next&#39; values through it. The helper allows only relative paths and absolute URLs whose scheme is http(s) and whose host matches the current request host; it rejects external hosts in absolute and protocol-relative form, non-http schemes (javascript:, data:, mailto:), userinfo tricks (http://localhost@attacker/), and backslash variants that some browsers normalize to forward slashes. Unsafe targets fall back to the internal browser index. A dedicated regression test exercises each accept/reject category and the original reporter PoC.</p> <p>This issue affects pgAdmin 4: from 6.0 before 9.16.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-12049 https://cve.radiocsirt.org/vuln/ghsa-7r93-vp6c-cw5m <p>Open redirect in pgAdmin 4&#39;s multi-factor authentication flow. The MFA validate and register endpoints honoured the user-supplied &#39;next&#39; query/form parameter without confirming the target pointed back inside pgAdmin, so an authenticated victim who clicked /mfa/validate?next=&lt;external&gt; -- a link typically delivered by phishing -- would be sent to an attacker-controlled host directly out of the trusted auth flow.</p> <p>The defect is a trusted-domain redirect, not a privilege bypass: the attacker gains no read/write access to pgAdmin or the victim&#39;s database, but the redirect launders the attacker&#39;s destination through pgAdmin&#39;s URL, which raises the success rate of credential-phishing follow-on against the victim.</p> <p>Fix introduces a same-origin _is_safe_redirect_url helper and gates every MFA redirect that consumes user-supplied &#39;next&#39; values through it. The helper allows only relative paths and absolute URLs whose scheme is http(s) and whose host matches the current request host; it rejects external hosts in absolute and protocol-relative form, non-http schemes (javascript:, data:, mailto:), userinfo tricks (http://localhost@attacker/), and backslash variants that some browsers normalize to forward slashes. Unsafe targets fall back to the internal browser index. A dedicated regression test exercises each accept/reject category and the original reporter PoC.</p> <p>This issue affects pgAdmin 4: from 6.0 before 9.16.</p> <p>Open redirect in pgAdmin 4&#39;s multi-factor authentication flow. The MFA validate and register endpoints honoured the user-supplied &#39;next&#39; query/form parameter without confirming the target pointed back inside pgAdmin, so an authenticated victim who clicked /mfa/validate?next=&lt;external&gt; -- a link typically delivered by phishing -- would be sent to an attacker-controlled host directly out of the trusted auth flow.</p> <p>The defect is a trusted-domain redirect, not a privilege bypass: the attacker gains no read/write access to pgAdmin or the victim&#39;s database, but the redirect launders the attacker&#39;s destination through pgAdmin&#39;s URL, which raises the success rate of credential-phishing follow-on against the victim.</p> <p>Fix introduces a same-origin _is_safe_redirect_url helper and gates every MFA redirect that consumes user-supplied &#39;next&#39; values through it. The helper allows only relative paths and absolute URLs whose scheme is http(s) and whose host matches the current request host; it rejects external hosts in absolute and protocol-relative form, non-http schemes (javascript:, data:, mailto:), userinfo tricks (http://localhost@attacker/), and backslash variants that some browsers normalize to forward slashes. Unsafe targets fall back to the internal browser index. A dedicated regression test exercises each accept/reject category and the original reporter PoC.</p> <p>This issue affects pgAdmin 4: from 6.0 before 9.16.</p> https://cve.radiocsirt.org/vuln/ghsa-7r93-vp6c-cw5m https://cve.radiocsirt.org/vuln/opensuse-su-2026:11508-1 <p>pgadmin4-9.17-1.1 on GA media</p> <p>pgadmin4-9.17-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11508-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2005 <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in pgAdmin ausnutzen, um beliebigen Code mit Benutzer- oder Administratorrechten auszuführen, Sicherheitsmaßnahmen zu umgehen, SQL-Injection- und Cross-Site-Scripting-Angriffe durchzuführen, Benutzer auf bösartige Websites umzuleiten, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.</p> <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in pgAdmin ausnutzen, um beliebigen Code mit Benutzer- oder Administratorrechten auszuführen, Sicherheitsmaßnahmen zu umgehen, SQL-Injection- und Cross-Site-Scripting-Angriffe durchzuführen, Benutzer auf bösartige Websites umzuleiten, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2005