Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
HIGH severity

GHSA-h8hx-2c5r-32cf

HIGHFix: TrestleAdmin/trestle-auth@cb95b05

GHSA-h8hx-2c5r-32cf is a high-severity (CVSS 8.1) Cross-Site Request Forgery (CSRF) vulnerability in trestle-auth. O3 Security confirms whether GHSA-h8hx-2c5r-32cf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Request Forgery (CSRF) in trestle-auth

Also known asCVE-2021-29435
Published
Apr 13, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
💎trestle-auth

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials.

Patches

The vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemstrestle-auth0.4.0&&< 0.4.20.4.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trestle-auth. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update trestle-auth to 0.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h8hx-2c5r-32cf is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-h8hx-2c5r-32cf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h8hx-2c5r-32cf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials. ### Patches The vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems. ### For more information If you have any questions or comments about this advisory: * Open an issue in [trestle-auth](https://github.com/TrestleAdmin/trestle-auth/issues) * Email the maintainer at
O3 Security · Impact-Aware SCA

Is GHSA-h8hx-2c5r-32cf in your dependencies?

O3 detects GHSA-h8hx-2c5r-32cf across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-h8hx-2c5r-32cf: Cross-Site Request… | O3 Security