{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-52723 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-52723 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-52723 is a critical authentication bypass vulnerability in fbeta-GmbH ePA3-Service-OpenSource, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-52723 and fix it if it is affected.\n\nWhat it is: CVE-2026-52723 is a critical authentication bypass vulnerability in fbeta-GmbH ePA3-Service-OpenSource, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-52723 in the wild and no public exploit code.\n\nAffected product: fbeta-GmbH ePA3-Service-OpenSource. 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-2026-52723/ (Markdown: https://insights.sbomify.com/CVE-2026-52723/index.md)","id":"CVE-2026-52723","markdown":"https://insights.sbomify.com/CVE-2026-52723/index.md","name":"CVE-2026-52723","record":{"aliases":["GHSA-q2jw-6c4w-86jc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ePA 3.x Integration","requires_auth":"none","summary":"A network attacker can bypass VAU server authentication via circular certificate trust to intercept and modify encrypted medical data traffic.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration performs VAU server certificate validation in app/vau/VAUProtokoll.py without anchoring the signed_vau_server_pub_keys and AUT_VAU_CertData certificate path to independent trusted material. A network-positioned attacker between the DiGA backend and the ePA system can intercept the VAU handshake, supply attacker-controlled certificate and key material, and satisfy the circular trust relationship. Because TLS certificate verification is also disabled in affected versions, no independent server-authentication layer prevents the attack. The attacker can impersonate the VAU server, control the negotiated session keys, and read or modify all encrypted VAU traffic. This issue is fixed in version 1.3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ePA 3.x Integration: VAU Server Authentication Bypass via Circular Certificate Trust","id":"CVE-2026-52723","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"kuma-dp connects to control plane without verifying TLS certificate when no CA is configured","id":"CVE-2026-52724"},"packages":[],"prev":{"headline":"Gstreamer1-plugins-bad-free: gstreamer: signed integer overflow in vmnc decoder cursor payload handling","id":"CVE-2026-52722"},"products":["ePA3-Service-OpenSource"],"published":"2026-08-18","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["fbeta-GmbH"]},"summary":"A network attacker can bypass VAU server authentication via circular certificate trust to intercept and modify encrypted medical data traffic.","url":"https://insights.sbomify.com/CVE-2026-52723/"}