{"answers":{"affected":"3 open source packages ship an affected version, including lemur.","exploited":"There is no known exploitation of CVE-2026-48508 in the wild and no public exploit code.","fix":"Upgrade lemur to 1.9.1 or later.","what":"CVE-2026-48508 is a high-severity missing authorization vulnerability in Netflix lemur, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48508 and fix it if it is affected.\n\nWhat it is: CVE-2026-48508 is a high-severity missing authorization vulnerability in Netflix lemur, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-48508 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lemur (PyPI): affected all versions; fixed in 1.9.1\n- lemur (PyPI): affected all versions; fixed in 1.9.1\n- lemur (PyPI): affected all versions; fixed in 1.9.1\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-48508/ (Markdown: https://insights.sbomify.com/CVE-2026-48508/index.md)","id":"CVE-2026-48508","markdown":"https://insights.sbomify.com/CVE-2026-48508/index.md","name":"CVE-2026-48508","record":{"aliases":["GHSA-qcqw-jwxc-2hqg","PYSEC-2026-2588"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"TLS certificate management","requires_auth":"low_privilege","summary":"Read-only users can create root CAs and upload certificates due to a permission bypass when specific security flags are disabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Lemur manages TLS certificate creation. Prior to 1.9.1, StrictRolePermission and AuthorityCreatorPermission in lemur/auth/permissions.py call flask_principal.Permission.__init__() with zero Need objects when ADMIN_ONLY_AUTHORITY_CREATION and LEMUR_STRICT_ROLE_ENFORCEMENT are unset because both flags default to False. Flask-Principal Permission.allows() returns True when self.needs is empty, so the .can() authorization gate permits every authenticated identity, including the read-only role. A read-only user can access POST /api/1/authorities, POST /api/1/certificates/upload, POST /api/1/pending_certificates//upload, POST /api/1/notifications, PUT or DELETE /api/1/notifications/, and POST /api/1/domains to create root Certificate Authorities, upload arbitrary certificates, create or edit notifications that reach an SSRF sink, and create domain entries. Explicitly setting either flag to False continues to opt into the permissive behavior. This issue is fixed in version 1.9.1.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Lemur: Authorization bypass in StrictRolePermission / AuthorityCreatorPermission","id":"CVE-2026-48508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"MessagePack-CSharp: ASP.NET Core MessagePackInputFormatter defaults to TrustedData for HTTP request bodies","id":"CVE-2026-48509"},"packages":[{"ecosystem":"PyPI","fixed":["1.9.1"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":null,"source":"GHSA-qcqw-jwxc-2hqg"},{"ecosystem":"PyPI","fixed":["1.9.1"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"GHSA-qcqw-jwxc-2hqg"},{"ecosystem":"PyPI","fixed":["1.9.1"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"PYSEC-2026-2588"}],"prev":{"headline":"Snipe-IT: Bulk editing users allowed `ldap_import` and `activated_in` bulk editing users","id":"CVE-2026-48507"},"products":["lemur"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["Netflix"]},"summary":"Read-only users can create root CAs and upload certificates due to a permission bypass when specific security flags are disabled.","url":"https://insights.sbomify.com/CVE-2026-48508/"}