Hollo security updates: 0.8.18 and 0.9.26
If you run Hollo, update to 0.8.18 or 0.9.26 now. These releases fix two vulnerabilities in Hollo: stored cross-site scripting (GHSA-534j-mgxh-5pj3) and server-side request forgery in link previews (GHSA-wh53-vmw6-c48j). They also include four security fixes from Fedify.
For GHSA-534j-mgxh-5pj3, Hollo rendered some remote post bodies and author display names as HTML without sanitizing or escaping them. A remote account could supply content that runs a script in a visitor's browser when the visitor opens an affected post or profile page. The fix sanitizes post bodies and escapes display names when rendering them, including in replies, shares, and quotes already stored in the database. It also escapes custom emoji image URLs used in HTML attributes.
For GHSA-wh53-vmw6-c48j, a remote account whose post Hollo processed could cause Hollo to send preview requests to services on its own host or private network. Large preview responses could also consume server memory. Hollo now checks the initial destination and each redirect, restricts connections to validated public addresses, and limits responses to 1 MiB after decompression. The preview fetch has its own address checks, separate from Fedify's ALLOW_PRIVATE_ADDRESS setting.
Hollo uses Fedify to resolve remote handles, deliver outgoing activities, and look up NodeInfo when it records a remote instance. Remote servers that stalled could tie up those operations. The updated dependency gives WebFinger lookups a 10-second deadline and bounds remote handle resolution (GHSA-9pmv-w936-hj3f). Activity delivery now has a 30-second deadline per attempt, with timed-out attempts subject to the configured retry schedule (GHSA-fq5h-gjhp-g75x). NodeInfo lookups have a 10-second default deadline and stop following redirect loops (GHSA-64hq-2hgr-q4pm).
Fedify also tightened origin checks on embedded ActivityPub objects (GHSA-r388-57j3-5fgp). When processing remote objects, it now applies those checks even if the parent has no id, so it no longer trusts embedded objects from another origin in that case. See the Fedify security announcement for details on the upstream fixes.
On the supported Hollo release lines, upgrade if you run 0.8.x through 0.8.17 or 0.9.x through 0.9.25. 0.8.18 and 0.9.26 are the first releases on their respective lines to include these fixes and the versions we recommend. They ship with Fedify 2.1.32 and 2.2.21, respectively. Hollo 0.7.x and earlier are no longer supported under the Hollo security policy; move to a supported line.
For 0.8.x deployments, update to 0.8.18:
docker pull ghcr.io/fedify-dev/hollo:0.8.18For 0.9.x deployments, update to 0.9.26:
docker pull ghcr.io/fedify-dev/hollo:0.9.26Recreate your Hollo container after pulling the new image. With Docker Compose, update the image tag in your Compose file and run docker compose up -d. For source deployments, check out the corresponding release tag, run pnpm install --frozen-lockfile with the pnpm version pinned in that tag's package.json, run pnpm run build, and restart the server.
If you have a large 0.9.x database and are upgrading from before 0.9.20, follow the 0.9.20 index preparation instructions before starting the new version to avoid blocking writes during the automatic migration.
Thanks to @carfeii for reporting the stored cross-site scripting issue and to @thegruber for reporting the link preview issue to Hollo. Thanks to zx (@manus-pi) for reporting the WebFinger, delivery, and NodeInfo issues to Fedify, to @manus-use for reporting the WebFinger and NodeInfo issues, and to @hongminhee for reporting the embedded-object origin-check issue.
If anything is unclear, ask below.
github.com
manus-use - Overview
Security Researcher | Sharing practical Cybersecurity Knowledge - manus-use

