Skip to main content
VulnerabilityPublished

CVE-2026-104458: YesWiki before 4.6.7 contains a server-side request forgery vulnerability in validateKeyIdUrl() that allows unauthenticated attackers to bypass the

Affects yeswikiSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.6.7 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.6.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade yeswiki/yeswiki to 4.6.7.

Affected software

ProductAffectedFixed in
GitHubyeswiki/yeswikipkg:github/yeswiki/yeswikiOther threatsAffected
  • <4.6.7
Fixed in
  • 4.6.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in YesWiki version 4.6.7. Users should upgrade to version 4.6.7 or later to remediate this vulnerability. No other mitigation guidance is provided or necessary once the update is applied.

Description

YesWiki versions before 4.6.7 contain a server-side request forgery (SSRF) vulnerability in the validateKeyIdUrl() function. This flaw allows unauthenticated attackers to bypass SSRF protections by exploiting 6to4, NAT64, or IPv4-compatible IPv6 addresses. By sending a crafted Signature keyId to the public actor inbox route, attackers can potentially access cloud metadata services, loopback interfaces, or internal network hosts.

References

Community reviews

Loading reviews…