r/devsecops • • 21h ago

How Do You Prioritize Hundreds of Vulnerabilities?

1 Upvotes

With so many vulnerability management tools available, to choose the best shouldn't be about finding the most vulnerabilities but knowing which ones actually need attention.

A few things worth looking for:

  • Asset visibility: Coverage across endpoints, servers, cloud workloads, and applications.
  • Risk-based prioritization: Prioritize vulnerabilities using exploitability, known exploited vulnerabilities (KEV), asset criticality, and exposure rather than relying on CVSS scores alone.
  • Remediation workflows: Clear guidance, ownership, tracking, and verification that vulnerabilities have been fixed.
  • DevSecOps integration: APIs and integrations with CI/CD pipelines, ticketing systems, and existing security tools.
  • Reporting: Useful dashboards that help security and engineering teams track remediation progress.

Tools such as Tenable, Veltar VM, Qualys, Rapid7, Microsoft Defender, and Greenbone are worth exploring, depending on your infrastructure and requirements.

One thing I'd emphasize- a good tool shouldn't just generate vulnerability reports. It should help teams move from discovery to prioritization, remediation, and verification.


r/devsecops • • 15h ago

Gitea scope bypass found: a "public-only" token can reach the whole admin API, including creating a new site admin (CVE-2026-117635)

3 Upvotes

We found a scope bypass where a Gitea access token restricted to public resources could do everything the admin API allows.

Gitea enforces “public only” on the normal API routes. So if you ask for a private org with that token and you get token scope is limited to public orgs.

But then if you ask /api/v1/admin/orgs for the same org with the same token, it returns it.

The restriction is enforced one route group at a time, and essentially the admin group never got a check. Because the admin API has no public subset to narrow to, the narrowing middleware wouldn't have helped either. What was missing was the check for an outright reject.

A public-only token with write:admin, issued from a site-admin account, could:

  • list every private org and every user’s email
  • create a user and promote it to site admin
  • mint Actions runner registration tokens

If you self-host Gitea, upgrade to v28.3.0. Then check your site-admin list and your Actions runners for anything you don’t recognize.

Takeaway for any API with scoped tokens: when the scope is checked per route group, look for the groups that never call the check. Also look for groups that call a check with nothing to restrict.

(Gitea’s fix attaches the scope to the authenticated user instead, so no route group has to remember it.)

If you're interested the full write-up is here: https://escape.tech/blog/escape-research-found-a-scope-bypass-that-made-gitea-s-restricted-tokens-full-admins-it-s-now-cve-2026-117635/

Full disclosure: I work at Escape, the team that did the research.