How many CVEs have patched configure_logging?

3 published CVEs changed configure_logging in Significant-Gravitas/AutoGPT, in 1 distinct patches totalling 81 changed lines, between 2026 and 2026.

What is the latest CVE that changed configure_logging?

CVE-2025-32425 (AutoGPT has missing Docker log rotation on platform containers that allows host disk-exhaustion DoS), published 2026-05-13, changed lines 143 to 180 of autogpt_platform/autogpt_libs/autogpt_libs/logging/config.py.

How does configure_logging compare to the rest of Significant-Gravitas/AutoGPT?

Significant-Gravitas/AutoGPT has 14 CVEs with a located fix in total; 3 of them changed configure_logging.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Significant Gravitas
Autogpt
Configure_logging

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Significant Gravitas
Autogpt
Configure_logging

configure_logging in Significant-Gravitas/AutoGPT: Patched by 3 CVEs

Significant-Gravitas/AutoGPT

Function

configure_logging

Name: configure_logging in Significant-Gravitas/AutoGPT: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

autogpt_platform/autogpt_libs/autogpt_libs/logging/config.py

Last patched May 13, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

configure_logging in Significant-Gravitas/AutoGPT was changed by 3 published CVE fixes in 2026, in 1 distinct patches that added or removed 81 lines in total.

Significant-Gravitas/AutoGPT has 14 CVEs with a located fix in total, so 21% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed configure_logging, newest first, with the lines each fix touched.

AutoGPT has missing Docker log rotation on platform containers that allows host disk-exhaustion DoS
CVE-2025-32425 · lines 143–180 · +21 −6 in 3 hunks
Medium · CVSS 5.1
EPSS 0.2%2026-05-13
Redos (Regular Expression Denial of Service) at Code Extraction Block in significant-gravitas/autogpt
CVE-2026-26006 · lines 143–180 · +21 −6 in 3 hunks
Medium · CVSS 6.5
EPSS 0.7%2026-02-10
AutoGPT has a DoS vulnerability in ReadRSSFeedBlock
CVE-2025-32393 · lines 143–180 · +21 −6 in 3 hunks
High · CVSS 8.7
EPSS 0.4%2026-02-05

Get an alert when the next CVE fix lands in Significant-Gravitas/AutoGPT, with the patched functions.

Monitor AutoGPT CVEs

Other hotspots in the repository

Functions in Significant-Gravitas/AutoGPT changed by the most CVE fixes.

_split_text3 CVEs · autogpt_platform/backend/backend/blocks/llm.py parse_feed3 CVEs · autogpt_platform/backend/backend/blocks/rss.py run3 CVEs · autogpt_platform/backend/backend/blocks/code_extraction_block.py run3 CVEs · autogpt_platform/backend/backend/blocks/iteration.py extract_code3 CVEs · autogpt_platform/backend/backend/blocks/code_extraction_block.py run3 CVEs · autogpt_platform/backend/backend/blocks/text.py

All patched functions in Significant-Gravitas/AutoGPT

Frequently asked questions

Common questions about CVE fixes to configure_logging.

How many CVEs have patched configure_logging?: 3 published CVEs changed configure_logging in Significant-Gravitas/AutoGPT, in 1 distinct patches totalling 81 changed lines, between 2026 and 2026.
What is the latest CVE that changed configure_logging?: CVE-2025-32425 (AutoGPT has missing Docker log rotation on platform containers that allows host disk-exhaustion DoS), published 2026-05-13, changed lines 143 to 180 of autogpt_platform/autogpt_libs/autogpt_libs/logging/config.py.
How does configure_logging compare to the rest of Significant-Gravitas/AutoGPT?: Significant-Gravitas/AutoGPT has 14 CVEs with a located fix in total; 3 of them changed configure_logging.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

autogpt_platform/autogpt_libs/autogpt_libs/logging/config.py on GitHub (opens in a new tab)
All patched functions in Significant-Gravitas/AutoGPT
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track Significant-Gravitas/AutoGPT CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other hotspots in the repository
FAQ
References