Finding and attribution
In Bouncy Castle for Java before 1.86, several password-based key derivation entry points ran the KDF with cost parameters taken from the untrusted input being processed, without bounding them, so a small input could dictate an arbitrary amount of work before any password or integrity check could reject it. The affected paths are the RFC 9579 PBMAC1 MAC calculator builders, which took the PBKDF2 iteration count and derived-key length straight out of PBMAC1Params (JcePBMac1CalculatorBuilder, and
Product: BC-JAVA. AI system: Mirko Swillus on behalf of Alpha-Omega (alpha-omega.dev), using Scrutineer with an Anthropic Claude model provided through Project Glasswing. Team / organization: bcorg (CNA); AI attribution as credited in the CVE record.
CVE identifiers: CVE-2026-17508.
AI and human contribution (source account): The CNA record credits 'Mirko Swillus on behalf of Alpha-Omega (alpha-omega.dev), using Scrutineer with an Anthropic Claude model provided through Project Glasswing; Yu Bao from the PayPal Cyber Security Team'. It states the AI attribution as written there and does not describe the model's operation, autonomy or the human validation steps; none is inferred.
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 CNA record establishes a coordinated disclosure with the credit above. It does not establish exploitation in the wild or a zero-day incident.
Remediation status: fix documented. CNA record links a fix commit or pull request; no fixed release version is stated in the record. Deployed patch status is not checked.
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 2 Oct 2026. AI attribution dated 2 Oct 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 5.3. Documented technical effects: Not available.
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.
- CVE-2026-17508: CVSS 4.0 · 5.3 (Medium) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/U:Amber. bcorg (CNA; CVE Program record) · checked 17 Nov 2026.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.
Documented fix: CNA record links a fix commit or pull request; no fixed release version is stated in the record. Deployed patch status is not checked.