01Archive
Findings
Vulnerabilities and bugs that Ugur’s AI agents found in open-source projects. Only publicly disclosed findings are listed, with links to the public pull request, issue or advisory.
54 public findings across 47 projects. 210 private security reports sent, through GitHub private vulnerability reporting (137), email to project security contacts (71), GitLab confidential issues (1) and project security reporting forms (1). 3 fix PRs merged. 69 security reports accepted by maintainers, 44 published as advisories (as of 20 November 2026). Download as JSON
- 54public findings
- 47open-source projects
- 9ecosystems
- 3merged fix PRs
- 210private security reports sent
- 69security reports accepted, 44 published
- latest disclosure, 2026
By ecosystem
- JavaScript 15
- Go 13
- Python 7
- Rust 6
- PHP 5
- C 4
- Java 2
- C++ 1
- .NET 1
Severity scaleInfoLowMediumHighCritical
-
METS-GBS backend resizes page images to the size declared in the OCR data without a pixel limit
docling-project/docling · Security
The METS-GBS backend takes the page size from the hOCR page bbox and resizes the page image to that size with no upper limit (CWE-400, CWE-770). A METS-GBS archive of less than 200 KB that declares a very large page can make conversion allocate gigabytes of memory. The max_image_pixels limit added in 2.142.1 is not used by this backend, and METS-GBS is enabled in the default converter. This is a denial of service for an application that converts untrusted METS-GBS archives; confidentiality and integrity are not affected. Affected versions are docling >= 2.45.0, < 2.151.1 and docling-slim >= 2.92.0, < 2.151.1. Fixed by the maintainers in 2.151.1: the backend checks the page image size and the declared page size against max_image_pixels before it resizes, and skips a page over the limit.
-
Vendored QtWebApp in RemoteControl: pre-auth null dereference on empty multipart file part, and Windows path traversal in StaticFileController
Stellarium/stellarium · Security
The RemoteControl plugin’s vendored QtWebApp HTTP server dereferences a null pointer when a multipart file part is closed by a boundary with no data line, and this parsing runs before the plugin’s password check. On Windows, StaticFileController can serve files outside its document root through backslash-separated parent-directory segments. Both matter only when a user has enabled the plugin, which is off by default; the findings come from source review and were fixed in 26.3.320.
-
Legacy JSON decoder replays unvalidated method names, allowing arbitrary file writes
pasqal-io/Pulser · Security
pulser.json.coders.PulserDecoder replayed method names from the JSON “calls”/“to_build_calls” lists and from __submodule__/__name__ without checking them against an allowlist (CWE-470, CWE-73). A crafted legacy-format document could make the decoder call Sequence.draw or Register.draw with an attacker-chosen fig_name, writing a matplotlib figure file to any path the process can write. The file content is not meaningfully controllable, and there is no code execution. The abstract-representation serializer is not affected. The fix adds SUPPORTED_SEQUENCE_CALLS and SUPPORTED_SUBMODULE_METHODS allowlists. Affected pulser-core (pip) versions are <= 1.10.0. Fixed in 1.10.1, with backports 1.9.2, 1.8.1, 1.7.3 and 1.6.7. Versions older than 1.6 are not patched.
-
mcp-server-fetch robots.
txt path-canonicalization bypass modelcontextprotocol/servers · Security
mcp-server-fetch matches robots.txt rules against the request path exactly as the client spelled it, while a typical origin resolves the path before serving, so alternate spellings like //private can pass Disallow: /private and return the body. Affected versions >= 0.6.1, < 2026.11.11. Patched in 2026.11.11.
-
Archive extraction writes outside the destination via existing symlinks
xixu-me/tzst · Security
extract_archive() can write files outside the destination directory through symlinks that already exist there (CWE-22, CWE-59). Fixed in 1.3.4.
-
Insecure direct object reference
l4rm4nd/VoucherVault · Security
An authenticated user who knows a transaction UUID can delete another user’s transaction because delete_transaction does not check ownership. Affected versions <= 1.30.5.
-
BCC addresses exposed in message headers
zou-yu/worker-mailer · Security
BCC addresses are written into the SMTP DATA headers, exposing them to all recipients (CWE-200).
-
Unauthenticated read of secret settings
HoshinoSuzumi/chronoframe · Security
An unauthenticated GET of settings marked isSecret can return secret values, including the GitHub OAuth client secret. Affected versions <= 1.1.2. Fixed in 1.2.0.
-
Setting .
value on a code-input element writes it as unescaped HTML (DOM XSS) WebCoder49/code-input · Security
Under some conditions, setting the value of a code-input element from JavaScript inserts that value into the DOM as unescaped HTML, so script in the value can run with access to the whole page. Fixed in 2.10.0 and backported to earlier minor lines.
-
Deprecated rainbowText template writes color names and delimiters as unescaped HTML (DOM XSS)
WebCoder49/code-input · Security
When the deprecated codeInput.templates.rainbowText (rainbow_text) template is used with user-provided color names or a user-provided delimiter, that HTML is added to the DOM unescaped and can run script with access to the page. Fixed in 2.10.0 with backports to older lines.
-
Deprecated characterLimit template writes data-overflow-msg as unescaped HTML (DOM XSS)
WebCoder49/code-input · Security
When the deprecated codeInput.templates.characterLimit (character_limit) template is used with a user-provided data-overflow-msg, that value is added to the DOM unescaped and can run script with access to the page. Fixed in 2.10.0 with backports to older lines.
-
MyAuthenticator: unauthenticated passkey registration granted an admin session
IAMSDR/MyAuthenticator · Security
The /api/webauthn/register endpoint accepted passkey registration without authentication, and a successful registration produced an admin session, so anyone could take over the instance (CWE-306).
-
DOCTYPE internal subset parser differential
rgrove/parse-xml · Security
The parser handles the DOCTYPE internal subset differently from other XML parsers, which can let crafted documents be interpreted inconsistently.
-
Credentials forwarded on cross-origin and HTTPS-to-HTTP redirects
fent/node-miniget · Security
Authorization and cookie headers are kept when following redirects to another origin or from HTTPS to HTTP.
-
XSS via HTML-attribute escaping bypass in iframe srcdoc (entity re-parsing)
casid/jte · Security
Attribute escaping inside iframe srcdoc can be bypassed because the srcdoc value is entity-decoded and re-parsed as HTML. Fixed in 3.2.5.
-
Scripts() sanitizer bypass
mrz1836/go-sanitize · Security
Scripts() is documented to remove script, iframe, embed, and object tags, but through v1.6.0 it left those elements in place, so script content can survive sanitization. Fixed in 1.6.1.
-
#{} interpolation output is not HTML-escaped in text and attribute values (XSS)
mattn/go-slim · Security
Values interpolated with #{} in text and attribute positions were emitted without HTML escaping, allowing script injection from user-controlled data. Fixed in 0.0.5.
-
TokenStore::
verify() skips CSRF checks on empty POST bodies phpgt/Csrf · Security
TokenStore::verify() skipped CSRF checks when the POST body was empty, so empty-body and file-only multipart POSTs bypassed verification (CWE-352).
-
CRLF injection in request header values and referrer
phpgt/Fetch · Security
Request header values and the referrer are not checked for CR/LF, allowing HTTP header injection and request splitting (CWE-93, CWE-113).
-
Unbescape Java Properties key escaping leaves '=' unescaped (key injection)
unbescape/unbescape · Security
escapePropertiesKey and escapePropertiesKeyMinimal wrote '=' in Java Properties keys without escaping it, so a parser such as java.util.Properties ends the key there and treats the rest as the value. Untrusted text written as a key can set or override configuration entries. Affected versions 0.5 to 1.1.6.RELEASE. Patched in 1.1.7.RELEASE.
-
PASERK local-pw/
secret-pw unwrap trusts attacker KDF cost parameters daviddesmet/paseto-dotnet · Security
Paserk.Decode for local-pw/secret-pw runs Argon2id or PBKDF2 using mem/ops/para or iteration counts from the untrusted PASERK before the tag is checked, with no upper bound (CWE-400, CWE-770).
-
MyFit: mesocycle update accepted unfiltered Prisma input, allowing account takeover
WhyAsh5114/MyFit · Security
The mesocycles.editById endpoint passed a client-supplied Prisma MesocycleUpdateInput through without filtering. A logged-in user could use nested user connect and update operations to change another user’s account, leading to account takeover (CWE-639, CWE-915). Fixed in 3.22.1.
-
caomei-auth: SSO trustEmailVerified with open /
sso/ register enables account takeover CaoMeiYouRen/caomei-auth · Security
SSO provider registration at /sso/register was open to any logged-in user while trustEmailVerified was enabled. An attacker could register an SSO provider that asserts a victim’s email address, sign in as that user and take over the account (CWE-287, CWE-862). Fixed in 1.13.6.
-
Recovery codes are not invalidated after a successful two-factor challenge
stephenjude/filament-two-factor-authentication · Security
A recovery code that passed the two-factor challenge was not invalidated, so the same code could be reused across sessions (CWE-672, CWE-841).
-
Sticky Manager/
Factory/ Auth state under Laravel Octane PHP-Open-Source-Saver/jwt-auth · Security
Under Laravel Octane, tymon.jwt.manager, tymon.jwt.payload.factory and tymon.jwt.auth were registered as singletons, so request-local state (refreshFlow, sticky Factory claims, auth user) could leak across requests on the same worker. Public fix PR scopes those bindings, resets refreshFlow after refresh, and rebuilds claims on decode.
-
Authme: no-authentication mode encrypted the TOTP vault with a hard-coded empty key
Levminer/authme · Security
In no-authentication mode, Authme generated a zero-length encryption key, so the TOTP vault was effectively encrypted with a constant empty key and readable by anyone with local access to the vault file (CWE-321, CWE-330). Fixed in 7.1.2.
-
Authme: HTML injection through imported TOTP issuer and name fields
Levminer/authme · Security
Issuer and name values from an imported QR code or import file were rendered as HTML in the codes view, the edit view and the HTML export, allowing HTML injection from a crafted import (CWE-79). Fixed in 7.1.2.
-
CEmu: integer overflow in the cert_
field_ get length check allows an out-of-bounds read on a crafted ROM CE-Programming/CEmu · Security
cert_field_get in core/cert.c checked a certificate field’s length with an addition that could overflow a 32-bit integer. With a very large field length, the sum wrapped around, the bounds check passed, and callers read far past the end of the ROM buffer. Loading a crafted TI calculator ROM could therefore cause an out-of-bounds read and crash the emulator (SEGV). The attack is local and needs the user to load the ROM.
-
Heap out-of-bounds read in sdp_
decode_ multipart baresip/baresip · Security
A length underflow in sdp_decode_multipart allows a crafted multipart SDP body to trigger a heap out-of-bounds read. Fixed in 4.13.0.
-
ARC chain result published before all seal verifications complete
rspamd/rspamd · Bug
Public issue opened by the maintainer and labelled as a bug, crediting ucsurf for the original report. ARC verification could publish ARC_ALLOW and cache arc-allow before every ARC-Seal check had finished, so a seal that failed later left the allow result in place. Fixed by the maintainer in PR #6311 (https://github.com/rspamd/rspamd/pull/6311, merged 2026-10-14T10:18:20+03:00), which publishes the chain result only after all seal checks complete. Tracked as a bug, not a security advisory.
-
EGo: untrusted host can switch any enclave into a Marble and replace signed config files, env, and argv
edgelesssys/ego · Security
An EGo app that was not meant to run under MarbleRun could still be started in Marble mode by a malicious host. With a fake MarbleRun Coordinator, the host could then supply a crafted configuration and take integrity control of the app’s embedded files, environment variables, and arguments. The attestation evidence did not show whether the app ran standalone or as a Marble, so a remote verifier could not detect this. Fixed in 1.10.1, where Marble mode is an opt-in in enclave.json and changes the enclave’s UniqueID.
-
libpskc signature verification accepts embedded ds:KeyValue keys on xmlsec < 1.
3. 3 oath-toolkit/oath-toolkit · Security
pskc_verify_x509crt leaves xmlsec keyInfoReadCtx.enabledKeyData unrestricted; on xmlsec < 1.3.3 a PSKC signed with an embedded attacker ds:KeyValue reports valid_signature=1 against an unrelated trusted certificate, enabling forged OTP seed provisioning.
-
Missing handling for SVG animateTransform, animateMotion, and animateColor
rust-ammonia/ammonia · Security
The neutralization ammonia applied to the SVG animate and set elements was not applied to animateTransform, animateMotion and animateColor, so these could set an href to a javascript: URL and lead to stored XSS in applications that allow those tags. Fixed in 4.1.7 and 4.2.3. Reported by email to the maintainer.
-
Non-deterministic result from role policies due to cache collision
cerbos/cerbos · Bug
Public issue opened by the maintainer and labelled as a bug (kind/bug), crediting ucsurf for the report. When a role policy had two resource entries that both matched the requested kind, their first rules got the same cache key, so the second entry’s condition reused the first entry’s cached result and was never evaluated. Fixed by the maintainers in PR #3410 (https://github.com/cerbos/cerbos/pull/3410, merged 2026-10-12T10:48:51+03:00); the issue was closed on 2026-10-14T10:47:47+03:00. Tracked as a bug, not a security advisory.
-
bzip2-cli (bzip2 -d): decompressed output world-readable while written; setuid/
setgid bits copied onto invoker-owned file trifectatechfoundation/libbzip2-rs · Security
uncompress() creates output without a restrictive mode and only chmods at the end (TOCTOU read window); set_permissions_rust copies S_ISUID/S_ISGID without fchown, yielding an invoker-owned setuid file. Regressions vs C bzip2.
-
cron-parser: H/<step> (and H(min-max)/<step>) field expansion is still unbounded at parse time (heap-exhaustion DoS), incomplete fix of GHSA-r9w7-75q6-r884
harrisiirak/cron-parser · Security
The 256-value cap added in 5.10.1 for GHSA-r9w7-75q6-r884 runs after hashed fields are expanded, so it does not cover H/<step> or H(min-max)/<step>. Each such token expands to every value in its range before the cap applies, and a long expression of repeated tokens passed to CronExpressionParser.parse() can exhaust the Node.js heap and stop the process. Fixed in 5.10.2.
-
preact-render-to-string: non-string attribute values skip HTML entity encoding (SSR XSS)
preactjs/preact-render-to-string · Security
In the default renderToString and renderToStaticMarkup path, only string attribute values were HTML-entity encoded. Arrays and objects with a custom toString were converted to text and written into the attribute without encoding, so quote characters in them could break out of the attribute and inject markup during server-side rendering. This is distinct from the Preact core issue GHSA-36hm-qxxp-pg3m. Fixed in 6.8.1.
-
svg-sanitizer: UTF-16 input bypasses DOCTYPE stripping (incomplete fix of GHSA-9rjx-3jch-6vjf)
darylldoyle/svg-sanitizer · Security
The fixes for GHSA-9rjx-3jch-6vjf (stored XSS through DTD entities) and GHSA-v383-3rw5-q8rf (crash through DTD attribute declarations) removed <!DOCTYPE …> by searching the raw input bytes. libxml detects UTF-16 input from its byte order mark, and in UTF-16 the DOCTYPE bytes are interleaved with zero bytes, so the search found nothing and the internal DTD reached the parser. This brought back the DTD-based bypasses those fixes were meant to stop. Fixed in 1.1.0.
-
templ: javascript: URLs not sanitised in other URL attributes and mixed-case attribute names
a-h/templ · Security
templ sanitised string URLs only in a few attributes (a/link href, form action, object data) and only when the attribute name was lowercase. String values in other URL-bearing attributes, or in uppercase or mixed-case attribute names, were written without URL sanitisation, so javascript: URLs could pass through and run script. Fixed in v0.3.1100.
-
templ: {{ }} interpolation in a script template literal not escaped for ${
a-h/templ · Security
Inside a <script> element, {{ }} interpolation placed within a JavaScript template literal was not escaped for the ${ sequence. Attacker-controlled input could open a template expression and run arbitrary JavaScript in the page. Fixed in v0.3.1100.
-
README examples: handle a missing Authorization header
jshttp/basic-auth · Docs
Docs-only PR: in v3, parse() expects a string, so the README examples now pass req.headers.authorization ?? '' to match the upgrade instructions. A request without an Authorization header then gets undefined back (and a 401 in the http server example). Merged.
-
Crafted /
ByteRange with a negative length panics the fluent Verify(). Valid() API (unrecovered makeslice panic, DoS) digitorus/pdfsign · Security
A crafted /ByteRange with a negative length caused an unrecovered makeslice panic in the fluent Verify().Valid() API, so a malformed PDF could crash a service that verifies untrusted files (denial of service). Fixed in v1.0.0-rc5.
-
Untrusted (self-made) RFC 3161 timestamp sets the chain and revocation validation time, so expired or revoked signing certificates verify as Valid
digitorus/pdfsign · Security
An untrusted, self-made RFC 3161 timestamp set the time used for chain and revocation checks, so signatures from expired or revoked signing certificates could verify as Valid. Fixed in v1.0.0-rc5.
-
mimetype: CDF (OLE2) short-stream reader spends quadratic CPU on a crafted SSAT chain (DoS)
gabriel-vasile/mimetype · Security
When detecting CDF files (doc, ppt, xls), the short-stream reader followed a short-sector chain until its output reached the size of the whole short-stream pool, not the stream’s declared length. Each step walked the SSAT sector chain from the start without caching or bounds. A small crafted file could make detection take quadratic time and use a lot of CPU, in any application that sniffs the type of uploaded bytes. Fixed in v1.4.16.
-
anacrolix/
torrent remote peer crash via negative ut_ metadata piece or truncated metadata_ size anacrolix/torrent · Security
anacrolix/torrent did not check the lower bound of the bencode-decoded ut_metadata piece index or the extended-handshake metadata_size, which was only checked after truncation to uint32. A single small message from a remote peer can panic the peer connection goroutine and crash the embedding process. Affected versions < 1.62.0. Patched in 1.62.0.
-
Verifier treats p7.
Certificates[0] as the signer: a signature by any untrusted key is reported Valid + TrustedChain and attributed to a trusted third-party certificate digitorus/pdfsign · Security
The verifier used the first certificate in the signature (p7.Certificates[0]) as the signer, so a signature made with any untrusted key could be reported as Valid with a trusted chain and attributed to a trusted third-party certificate. Fixed in v1.0.0-rc4 (PR #175).
-
msgpack: unbounded MessagePack nesting causes a fatal goroutine stack overflow (DoS)
shamaton/msgpack · Security
The decoder had no limit on how deeply MessagePack arrays and maps could be nested. A small crafted input with deep nesting made decoding recurse until the goroutine stack overflowed, which is a fatal runtime error that cannot be recovered and stops the whole process. Fixed in v3 3.2.4 and v2 2.4.3.
-
XMSS^MT height-40 keys never report KeyExhausted after last signature
RustCrypto/signatures · Bug
Public bug report: after signing at the last XMSS^MT height-40 index, KeyExhausted is not raised and further signing returns Ok with an invalid signature. Open issue, no maintainer reply yet.
-
Superlinear CPU in ZipArchive::
new from many fake EOCD records (DoS) zip-rs/zip2 · Security
ZipArchive::new tried every fake end-of-central-directory candidate with no cap, so a small crafted file of EOCD records could take tens of seconds to open (CWE-407, DoS). Fixed in 9.0.4.
-
zip: AES HMAC verification skipped when the decompressor stops early
zip-rs/zip2 · Security
When reading an AES-encrypted entry, the HMAC authentication check ran only after the full stream was consumed. If the decompressor stopped early, the check was skipped, so an attacker could forge entry content that was accepted without knowing the password. Fixed in zip 9.0.1.
-
Quadratic CPU when BER/
CER-decoding a constructed BIT STRING pyasn1/pyasn1 · Security
Decoding a constructed BIT STRING from BER/CER input rebuilt the accumulated value for every fragment, so decoding cost grew quadratically with the number of fragments. Untrusted input could cause CPU exhaustion (denial of service). Fixed in pyasn1 0.6.5. ucsurf is credited as a co-reporter.
-
JWE decrypt: no limit on number of recipients (hardening)
latchset/jwcrypto · Security
JWE.decrypt tried every entry in the recipients array with no cap; public hardening PR adds an overridable default_max_recipients (10) and an early exit after the first successful decrypt.
-
Accept PKCS#8 v2 Ed25519 keys in Jwk::
from_ encoding_ key Keats/jsonwebtoken · Bug
Public bugfix PR: accept PKCS#8 v2 Ed25519 keys in Jwk::from_encoding_key. Open, no review yet.
-
Pass nil rand to rsa.
SignPKCS1v15 go-jose/go-jose · Bug
Public bugfix PR closed unmerged; maintainer plans one change with go.mod bump + more call sites.
If this work is useful to you, you can support it on Buy Me a Coffee.