Unauthenticated internal service probing via signature key URL
Published Sep 4, 2026 · Updated Sep 4, 2026
SSRF in YesWiki 4.6.2 through 4.6.5 allows remote attackers to make arbitrary HTTP requests through the ActivityPub inbox route. HttpSignatureService::verifySignature() parses the attacker-controlled Signature keyId and fetches that URL before validating its destination or verifying the signature. ActivityPub must be enabled on a Bazar form; exposed servers allow internal-service and cloud-metadata probing through timing and error responses.
Summary
What happened
SSRF in YesWiki 4.6.2 through 4.6.5 allows remote attackers to make arbitrary HTTP requests through the ActivityPub inbox route. HttpSignatureService::verifySignature() parses the attacker-controlled Signature keyId and fetches that URL before validating its destination or verifying the signature. ActivityPub must be enabled on a Bazar form; exposed servers allow internal-service and cloud-metadata probing through timing and error responses.
The record
- CVE
- CVE-2026-52769
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- YesWiki
- Product
- YesWiki
- Classifications
- CWE-918, T1046, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.6.2, < 4.6.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream end-to-end curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo