# CVE-2026-104440: YesWiki before 4.6.7 Blind SSRF via bazarlist API idtypeannonce Parameter

> Unauthenticated attackers can perform blind server-side request forgery via the bazarlist API to probe internal networks and access internal services.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-992m-5rj6-qxj2, GHSA-gw65-cpc7-hww6

## What is CVE-2026-104440?

CVE-2026-104440 is a medium-severity server-side request forgery vulnerability in yeswiki, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

YesWiki before 4.6.7 contains a blind server-side request forgery vulnerability that allows unauthenticated attackers to make arbitrary server-side requests via the idtypeannonce parameter of /api/entries/bazarlist. Because isValidURL() always returns true, attackers can supply internal URLs fetched by curl in loadURLContent() to probe internal networks and reach internal services or metadata endpoints.

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

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


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

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

## Is CVE-2026-104440 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104440 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104440 is a medium-severity server-side request forgery vulnerability in yeswiki, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104440 exists.

Affected product: yeswiki. 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-104440/ (Markdown: https://insights.sbomify.com/CVE-2026-104440/index.md)
```

## Sources

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

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