securityadvisoriesopen source
Eight advisories published this week
Eight security advisories in seven open-source projects went public between 23 and 29 October 2026. Here is what each one covers, the fixed versions, and what to upgrade.
Between 23 and 29 October 2026, maintainers of seven open-source projects published eight security advisories for issues we reported. Every one shipped with a fix. Thank you to each maintainer for the quick, careful work. If you use any of these packages, upgrade to the patched version.
At a glance
- 8 advisories in 7 projects, in JavaScript, Rust, Go and Python.
- 3 high, 3 medium, 2 low.
- Several more reports have been accepted and are still with maintainers. We will write about them once they are public.
preact-render-to-string: attribute encoding in SSR
Advisory: GHSA-6jrx-cvj9-5x2x, low. Affected: preact-render-to-string <= 6.8.0. Fixed: 6.8.1.
Only string attribute values were HTML-encoded during server-side rendering. Arrays or objects with a custom toString were written as-is, so quotes in them could break out of the attribute and inject markup.
zip: AES HMAC check skipped
Advisory: GHSA-c9rm-qm35-rhqf, medium. Affected: zip crate <= 8.6.0. Fixed: 9.0.1.
For AES-encrypted entries, the HMAC check ran only after the whole stream was read. If decompression stopped early, the check never ran, so forged entry content could be accepted without the password.
templ: two script and URL escaping gaps
Advisories: GHSA-jq3r-rjqp-mwgj (low, affects >= 0.3.850, <= 0.3.1070) and GHSA-94c2-xg24-pwhv (medium, affects <= 0.3.1070). Fixed: v0.3.1100.
Inside a <script> template literal, {{ }} interpolation did not escape ${, which could let input run JavaScript. Separately, javascript: URLs were only sanitised in a few lowercase attributes, so other URL attributes or mixed-case names let them through.
pyasn1: quadratic decoding of BIT STRING
Advisory: GHSA-2qm8-x737-gmw5, high (7.5). Affected: pyasn1 <= 0.6.4. Fixed: 0.6.5.
Decoding a constructed BIT STRING from BER/CER input rebuilt the value for every fragment, so cost grew quadratically. Untrusted input could exhaust CPU. We are credited as a co-reporter.
MyFit: mass assignment leading to account takeover
Advisory: GHSA-jhfj-c242-ghx4, high (8.1). Affected: <= 3.22.0. Fixed: 3.22.1.
The mesocycles.editById endpoint passed client input straight into a Prisma update. A logged-in user could use nested operations to change another user’s account.
caomei-auth: SSO registration and trusted email
Advisory: GHSA-785j-54p4-vxw9, high (8.1). Affected: >= 1.3.0, < 1.13.6. Fixed: 1.13.6.
Any logged-in user could register an SSO provider while trustEmailVerified was on. That provider could assert a victim’s email address and sign in as them.
bzip2-cli: output file permissions
Advisory: GHSA-4j37-jjpm-9865, medium. Affected: bzip2-cli <= 0.2.5. Fixed: 0.2.6.
When decompressing, bzip2 -d created the output file without a restrictive mode and set permissions only at the end, leaving a window where others could read it. It also copied setuid and setgid bits onto a file owned by the invoking user. Both differ from the original C bzip2.
What to do
- Check your lock files for the packages above and move to the fixed versions.
- If you run MyFit or caomei-auth yourself, upgrade first. Those two allow account takeover.
- For bzip2-cli, also review files decompressed on shared systems with older versions.
Follow along
Each finding has its own page on the findings page, with a timeline and a link to the advisory. The findings index has the same data as JSON, and the Atom feed announces new ones.
If you maintain one of these projects and something here is wrong, email info@uc.surf.
Machine-readable: Markdown