{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-5519 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5519 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5519 is a medium-severity vulnerability in ArgusTech BILGER, published on 16 Sep 2025."},"fix_prompt":"Check this codebase for CVE-2025-5519 and fix it if it is affected.\n\nWhat it is: CVE-2025-5519 is a medium-severity vulnerability in ArgusTech BILGER, published on 16 Sep 2025. \nExploitation: There is no known exploitation of CVE-2025-5519 in the wild and no public exploit code.\n\nAffected product: ArgusTech BILGER. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-5519/ (Markdown: https://insights.sbomify.com/CVE-2025-5519/index.md)","id":"CVE-2025-5519","markdown":"https://insights.sbomify.com/CVE-2025-5519/index.md","name":"CVE-2025-5519","record":{"aliases":["GHSA-rpx2-m5m5-r7ww"],"analysis":null,"analysis_generated_by":null,"assigner":"TR-CERT","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"Insertion of Sensitive Information Into Sent Data vulnerability in ArgusTech BILGER allows Choosing Message Identifier.\n\nThis issue affects BILGER: before 2.4.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information Disclosure in ArgusTech's BILGER","id":"CVE-2025-5519","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Open5GS AMF/MME emm_state_authentication assertion","id":"CVE-2025-5520"},"packages":[],"prev":{"headline":"IDOR in ArgusTech's BILGER","id":"CVE-2025-5518"},"products":["BILGER"],"published":"2025-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-05","vendors":["ArgusTech"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-5519/"}