{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2025-47729 in the wild since at least 12 May 2025.","fix":"No fix has been published for CVE-2025-47729 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Jun 2025.","what":"CVE-2025-47729 is a low-severity vulnerability in TeleMessage archiving backend, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47729 and fix it if it is affected.\n\nWhat it is: CVE-2025-47729 is a low-severity vulnerability in TeleMessage archiving backend, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2025-47729 in the wild since at least 12 May 2025.\n\nAffected product: TeleMessage archiving backend. 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-47729/ (Markdown: https://insights.sbomify.com/CVE-2025-47729/index.md)","id":"CVE-2025-47729","markdown":"https://insights.sbomify.com/CVE-2025-47729/index.md","name":"CVE-2025-47729","record":{"aliases":["GHSA-h5qv-qcjq-wcff"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TeleMessage archiving backend","requires_auth":"high_privilege","summary":"The TeleMessage archiving backend stores cleartext copies of user messages, exposing sensitive data despite claims of end-to-end encryption.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"text_message_archiver","vendor":"telemessage"}],"cvss":{"score":1.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-912","name":"Hidden Functionality"}],"description":"The TeleMessage archiving backend through 2025-05-05 holds cleartext copies of messages from TM SGNL (aka Archive Signal) app users, which is different functionality than described in the TeleMessage \"End-to-End encryption from the mobile phone through to the corporate archive\" documentation, as exploited in the wild in May 2025.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"TeleMessage TM SGNL Hidden Functionality","id":"CVE-2025-47729","indexable":true,"kev":{"dateAdded":"2025-05-12","dueDate":"2025-06-02","knownRansomwareCampaignUse":"Unknown","product":"TM SGNL","requiredAction":"Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.","vendorProject":"TeleMessage","vulnerabilityName":"TeleMessage TM SGNL Hidden Functionality Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in archiving backend","id":"CVE-2025-47730"},"packages":[],"prev":{"headline":"File Parsing Memory Corruption in CNCSoft-G2","id":"CVE-2025-47728"},"products":["archiving backend"],"published":"2025-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["TeleMessage"]},"summary":"The TeleMessage archiving backend stores cleartext copies of user messages, exposing sensitive data despite claims of end-to-end encryption.","url":"https://insights.sbomify.com/CVE-2025-47729/"}