Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2019-16355

MEDIUM

CVE-2019-16355 is a medium-severity (CVSS 5.5) Incorrect Default Permissions vulnerability in github.com/beego/beego. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2019-16355 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Beego has a file creation race condition

Published
Sep 16, 2019
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Blast Radius

2 pkgs affected
🐹github.com/beego/beego🐹github.com/astaxie/beego

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

Description

The File Session Manager in Beego 1.10.0 allows local users to read session files because of weak permissions for individual files.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/beego/beegoall versions1.12.2
🐹Gogithub.com/astaxie/beegoall versions1.12.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/beego/beego. 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 github.com/beego/beego to 1.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16355 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 CVE-2019-16355 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 CVE-2019-16355. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The File Session Manager in Beego 1.10.0 allows local users to read session files because of weak permissions for individual files.
O3 Security · Impact-Aware SCA

Is CVE-2019-16355 in your dependencies?

O3 detects CVE-2019-16355 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.