| Version | Supported |
|---|---|
| 0.3.x | Yes |
| 0.2.x | No |
| < 0.2 | No |
If you discover a security vulnerability in Forge, please do not open a public issue.
Instead, report it privately:
- Go to Security Advisories
- Or email: security@forge-lang.dev
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
We will acknowledge your report within 48 hours and provide a timeline for a fix.
Forge v0.3.0 is a young language. The following are documented limitations, not vulnerabilities:
- SQL queries use raw strings — no parameterized query API yet. Do not pass untrusted user input directly into
db.query()orpg.query(). - File system access is unrestricted —
fs.read/writecan access any path the process has permission for. - Shell execution via
sh()andexec.run_command()runs commands directly. Do not pass untrusted input. - HTTP server uses permissive CORS by default. Configure appropriately for production.
When using Forge:
- Sanitize all user input before passing to
db.query(),sh(), orfs.*functions - Use environment variables (
env.get()) for secrets, never hardcode them - Bind servers to
127.0.0.1for local development (this is the default)