Finding and attribution
Trilogy#escape mishandles strings in Shift_JIS, Windows-31J, Big5, GBK, and GB18030 because a multibyte continuation byte can overlap ASCII syntax. Applications are affected when attackers control the encoding of strings being escaped, or when using unsupported connection encodings. The advisory identifies unauthenticated SQL injection in affected Rails and Rack applications.
Product: Trilogy Ruby database driver. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and project maintainers.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The primary Trilogy maintainer advisory labels the report AI-assisted and directly credits Anthropic OSS Scanner as discovering it under ANT-2026-9KOHJMNW. Anthropic’s primary scanner page says it scans with its strongest models; the Oct 8 launch post names Claude Mythos among those models. No item-specific model is stated.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary maintainer published GHSA-744p-w4gc-m3gh on 2026-10-29 and directly credits Anthropic OSS Scanner (ANT-2026-9KOHJMNW); no CVE was assigned in the advisory.
Remediation status: fix documented. Trilogy 2.13.2 rejects the unsupported legacy connection encodings and fixes escaping. Projects unable to update can enforce encodings for strings passed to escape/query, as described by the advisory.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 29 Oct 2026. AI attribution dated 29 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: other.
Prerequisites / affected scope: Apps are affected when attacker-influenced strings are escaped under non-ASCII-compatible encodings or the connection uses such an encoding; the advisory documents unauthenticated SQL injection in those cases but does not specify resulting reads or writes..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Trilogy 2.13.2 rejects the unsupported legacy connection encodings and fixes escaping. Projects unable to update can enforce encodings for strings passed to escape/query, as described by the advisory.