Authenticated audit-log forgery via CRLF file identifier
Published Mar 16, 2026 · Updated Mar 16, 2026
Log injection in Danny Avila RAG API 0.7.0 allows remote authenticated users to forge audit entries through a crafted file_id. The ingestion routes write the form-data file_id value to application logs without neutralizing embedded carriage-return or line-feed characters. An authenticated file-ingestion request is required, and forged records can conceal activity or misdirect investigations; secondary attacks depend on an insecure downstream log viewer.
Summary
What happened
Log injection in Danny Avila RAG API 0.7.0 allows remote authenticated users to forge audit entries through a crafted file_id. The ingestion routes write the form-data file_id value to application logs without neutralizing embedded carriage-return or line-feed characters. An authenticated file-ingestion request is required, and forged records can conceal activity or misdirect investigations; secondary attacks depend on an insecure downstream log viewer.
The record
- CVE
- CVE-2026-4276
- Published
- Mar 16, 2026
- Updated
- Mar 16, 2026
- Vendor
- Danny Avila
- Product
- RAG API
- Classifications
- CWE-20, CWE-117, CWE-94, T1070
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2026CVE publishedPublication date reported by the CVE source.
- Mar 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo