Skip to content
Fencer Intel
medium 5.4

CVE-2026-97736 json

Authentication bypass via improper path matching

published 3mo ago modified 29d ago also EUVD-2026-86515 , GHSA-r27r-rr9v-vv37

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository tinyauthapp/tinyauth. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

tinyauth before 5.1.3 allows rule bypass by appending an allowed route string. This is caused by an unanchored regular expression.

Patch / fix

  • tinyauth tinyauth 5.1.3

Is CVE-2026-97736 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected products

  • tinyauth tinyauth

Classification

Weakness
  • CWE-777 Regular Expression without Anchors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of tinyauthapp/tinyauth published their own advisory on GitHub. Reviewed sources take precedence over it.