# CVE-2026-120416: AndyFactory newspaper4k Image Extractor image_extractor.py Article.parse server-side request forgery


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-hv55-xhhq-h9rr

## What is CVE-2026-120416?

CVE-2026-120416 is a medium-severity vulnerability in AndyFactory newspaper4k, published on 2 Nov 2026. 

### Official description

A security vulnerability has been detected in AndyFactory newspaper4k up to 0.9.6. This affects the function Article.parse of the file newspaper/extractors/image_extractor.py of the component Image Extractor. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. Upgrading to version 0.9.6.1 mitigates this issue. The name of the patch is eec5fab21897c14667c98f5ba1831ebd3a692dd4. Upgrading the affected component is advised. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

No fix has been published for CVE-2026-120416 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120416 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120416 and fix it if it is affected.

What it is: CVE-2026-120416 is a medium-severity vulnerability in AndyFactory newspaper4k, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120416 in the wild and no public exploit code.

Affected product: AndyFactory newspaper4k. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120416/ (Markdown: https://insights.sbomify.com/CVE-2026-120416/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120416
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120416
- OSV: https://osv.dev/vulnerability/CVE-2026-120416

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120416/
Summaries are generated and may contain mistakes; the official description above is the record.
